Perhaps you're getting a script error somewhere other than your closeCard handlers. A simple test here of closing a substack that executes a basic event during closeCard works as expected.
If you have multiple stacks to close, you might try closing them one-by-one individually and see if one causes the error. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 8/1/15, 12:31 PM, "Dr. Hawkins" <doch...@gmail.com> wrote: >Is there a way to lock messages and make it stick? > >In my quit routine so shut down, I handle some matters and then > >lock messages > >quit > > >The error aren't visible in the standalone, but in the IDE, the open >stacks >still get closeCard sent to them, causing error (because I've already shut >down the services) > > >-- >Dr. Richard E. Hawkins, Esq. >(702) 508-8462 >_______________________________________________ >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
