Ui.undo: Undoing op.destroy() Not Cooking Select or Parameter Chops

Hi all,
I’ve implemented an undo operation into an app for when the user deletes items. The item that’s deleted is actually a base component holding some custom parameters. I’m referencing these comps like this - "base_Cue*/null_CueInfo’ in a select chop, and like this ‘base_Cue*’ for a parameter chop.

Everything works fine as long as there is at least one item still being referenced by the chops.

Here are the cues present and happy -

They get removed as expected-

Performed undo on the deletion of all items and chops remain empty -

Anything I can do to jump start them aside from force cooking each?

Thanks!

I’ve reported this to dev.

In the meantime, you can use the ui.undo.addCallback system to add a callback into the undo chain. In that callback you can force cook. Is that what you’re already doing?

Hi Ivan,
That is what I’m doing now and it works fine.
Thanks!
-Tim

Cool. Glad to see people using this powerful system. Keep the feedback coming!

If anyone is interested in this topic and hasn’t gotten into using it yet, I just put together this tutorial on using the undo class.

1 Like