It doesn’t work in the IDE. I tried it. I set a checkpoint on the first line of that very handler, and I got the save dialog before the handler was triggered, which is why I put it in the frontScript. Besides, in the frontScript, it works no matter which stack or substack I close. This is important to me not just because I want to suppress the save dialog, but I actively set properties as a poor man’s stack global variables, so making sure the stack is saved when I close it is a necessary part of my applications, and giving the user the change to discard changes can adversely affect the operation of my applications.
Bob S On Feb 5, 2015, at 11:45 , FlexibleLearning.com<http://FlexibleLearning.com> <ad...@flexiblelearning.com<mailto:ad...@flexiblelearning.com>> wrote: The IDE can be easily suppressed with... on closeStackRequest lock messages save this stack pass closeStackRequest end closeStackRequest Hugh Senior FLCo _______________________________________________ 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
