PF_OutFlag_FORCE_RERENDER causes undo buffer entry?

Forum|Forum|6 years ago
July 17, 2019
1 reply
3803 views

I have a function that lets a user load data from a file after clicking a button. The function is wrapped in AEGP_StartUndoGroup(NULL)/AEGP_EndUndoGroup(); because there's no need for an undo. The load data function sets out_data->out_flags = PF_OutFlag_FORCE_RERENDER; to sync the loaded data on the UI and render threads.

This last step seems to create an undo entry, "Undo effects options change", despite the AEGP_StartUndoGroup being set to NULL. Undoing this subsequently causes a crash, apparently caused by the render thread not having the data.

I have wrapped everything I can find in AEGP_StartUndoGroup("{Unique name for each undo group}"), to see if I can isolate the function that causes the "effects options change" in the undo buffer. But no luck, it still says "Undo effects options change".

What ever it is that "effects options change" is, it seems to be undoable (which causes a crash) and re-doable (which lets the plugin run normally).

Is the UI/render thread sync itself an undoable function-- "effects options change"? Is there anyway to remove it from the undo stack? Or is there some other reason the undo removes the UI/render thread sync?

SDK

This topic has been closed for replies.

S

shachar carmi

Community Expert

errr... hmmm... wow. never seen that one.

this is a wild guess, but try putting and empty string (two consecutive

quotes signs) instead of a NULL in the undo group name. NULLs were dropped

as an option for creating an invisible undo group a while back, and an

empty string is used for the same purpose since.

On Wed, Jul 17, 2019 at 10:59 PM benp1711322 <forums_noreply@adobe.com>

benp1711322Author

Inspiring

Thanks Shachar.

I tried wrapping every function in uniquely named, non-null AEGP_StartUndoGroup statements.

This is the sequence of cmds I get with and without PF_OutFlag_FORCE_RERENDER:

WITH PF_OutFlag_FORCE_RERENDER:

*** --> GOT CMD: 13 > USER CHANGED PARAMS.

*** --> IN USER CHANGED PARAM WITH 274 (LOAD DATA)

*** --> IN LOAD DATA