Just off the top of my head... couldn't you clone the current card, so the cards of the stack containing the object who's properties are being altered would represent the history of changes. What would be required of the palette stack then would be some kind of timeline interface to the stack of cards containing the history of changes. If the user reverted to a particular point in time, then you would need to delete all the cards from the latest card to that selected card. (I'm guessing from the responses of others, that my response is naive).
I'm puzzled by Ken's remark about running out of IDs. What is the upper limit to the number of IDs? Bernard On Thu, Dec 8, 2011 at 3:01 AM, Alejandro Tejada <capellan2...@gmail.com>wrote: > Hi dunbarx, > > The Undo palette should, in theory, > record all the changes made by user > in the properties of a control, from > the most recent change to the very > beginning of his creation. > > Many Thanks for > your interest! > > Al > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/Creating-an-Undo-palette-tp4170194p4171407.html > Sent from the Revolution - User mailing list archive at Nabble.com. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
