Posted
Redo function.
preferably so that I can hit cmd shift and y at the same time and redo the undo that I just did, getting back all of the work that I 'undid' being a litle zealous with the undo button presses.
Thanks
Do., 02.04.2009 - 09:26 Permalink
I would love to have that too.
However, that would mean a huge engineering effort. Undo is relatively easy: It simply involves making a (partial) backup of the previous state. Redo would require to formalize every possible edit action - sort of scripting - in order to be able to replay them.
I will do some experiments with "undo of the undone". No idea if that works, but that would be a viable solution (if I don't miss anything important).
Fr., 03.04.2009 - 22:14 Permalink
Ideally a photoshop style undo / redo list where you could selectibvely undo certain changes without having to undergo all of the other steps. However I understand that might be a little more work :)
Redo of the undo's would be good.
I tend to work fairly fast so it's easy to go a step too far with the undo then loose something that you have spent a while putting together!
Sa., 04.04.2009 - 18:20 Permalink
That makes me wonder, is the "Synth Generator" component going to be properly unleashed in the future, or extended to be possibly linked/routed into a working document? Currently the only way to access it is to open the GPO velocity synth document. It would be nice to play around with formally at some point. I saw the fancy noise generators and figure recognition factory components and stuff when snooping around there. :)
So., 05.04.2009 - 22:12 Permalink
@tokyorose:
Scripting would be a nice perspective if we had a dozen or so primitives to build on, but actually there are more than a hundred already. That's too much a maintenance effort for a nice-to-have feature. Regarding redo, the "undo the undone" way might be viable (haven't tested yet).
@keith_phillips:
That editor is intended for testing only and is not supported. It is really buggy and not of much use at this time. We plan on supporting it in the future, very much in the way you suggested.