ResumeStack can be tricky. For instance, if you are tracing a resumeStack handler to debug it, every time you click back on to the stack in question, it will trigger the debugger and suspend the stack again! Rinse and repeat until you realize you can't trace a resumeStack handler without some special handling.
Bob S > On Jun 2, 2019, at 17:22 , Klaus major-k via use-livecode > <use-livecode@lists.runrev.com> wrote: > >> I’m not sure I understand the full range of events that “close” a card so >> that returning to it triggers “openCard.” Does this happen if I set an >> insertion point or select text in an unlocked field in a palette, or the >> user types there? Does it happen if I open a palette, or move a palette, or >> if the user clicks on the palette? > > See above, resumestack/suspendstack are the messages you could check, if > neccessary, in that case. > >> Many thanks. >> >> David Epstein > > Best > > Klaus > _______________________________________________ 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
