Got it thanks. That explains why I cannot even trap for closeStackRequest int othe substack script. The really odd thing is I can in the message box enter "close stack Time Calculator" and it closes without even bothering to ask if I want to save it, even when it is "dirty".
I was thinking of checking the dirty flag on idle, with a constant or property to enable or disable auto save, then check for the dirty flag on idle + time delay and auto save the stack. This really is only an issue with development. It's a hassle to switch to the pointer tool, save the substack then switch back to the browse tool. I complained about this behavior a couple times, but there really is no graceful way to do this without some kind of a kludge. Thanks for the suggestion. Bob S > On Oct 4, 2021, at 10:46 , J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On 10/4/21 12:14 PM, Bob Sneidar via use-livecode wrote: >> The stack in question is the only substack of a couple without a custom >> menu, so I am wondering if the last stack with a custom menu becomes the >> topStack?? > > If there is no custom menu then LC's menu takes over, and that's the one that > triggers the dialog. You might be able to solve the problem by using a custom > menu without much in it, maybe just File and Edit menus. > > If you're going to build a standalone then the problem shouldn't happen there > at all. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.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
