On 2/19/07 10:49 AM, "J. Landman Gay" <[EMAIL PROTECTED]> wrote:
> But for a product like Rev, where the current state could be > almost anything, it would be much harder. We'd need an engine change, I > think, and I like Richard's idea of having a property we could read that > would return the current state of, say, a whole stack, for instance. Couldn't you create a substack "undo" and set a series of custom properties to the mainStack as a binary+save this stack. In the beginning of stack development, this would be small overhead and the undo series could be purged when not needed any more. Added benefit is that the undo states would be persistent. Just make a tool bar button that would be clicked (or a message box command, or other trigger) Agreed that this is not the most elegant solution, but it might be better than continually saving versions. Jim Ault Las Vegas _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
