On 17/11/01 4:15 am, Nigel Perry <[EMAIL PROTECTED]> wrote: > Version: 1.1 MacOS 9 > Title: Changing a custom property isn't seen as a change when > deciding a stack needs saving > Desc: > > 1) Change a customProperty on a stack - I do this by calling a > handler in the stack from another stack > 2) Quit Revo > > What should happen: Asked to save stack with changed property > > What does happen: Stack not saved, change lost :-( > > I assume the stack should be seen as "dirty" and need saving. I've > tried this with the stack window open and closed (I "start using" the > stack to the window isn't normally visible). The stack properties > show the new property, but the stack is not saved on close. This > would seem to make the "persistent" nature of custom properties > pretty useless... > > Any workaround? (I'm off to a look fora "mark this stack dirty" command...)
Changing any property by script will not cause a warning that you need to save. You could set the gREVStackStatus[] array global variable in the development environment by script, or set your own global variable or property in your own scripts at run time. Regards, Kevin Kevin Miller <[EMAIL PROTECTED]> <http://www.runrev.com/> Runtime Revolution Limited - Power to the Developer! Tel: +44 (0) 870 747 1165. Fax: +44 (0)1639 830 707. _______________________________________________ improve-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/improve-revolution
