The script is not in the stack being deleted. Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
On Mon, Feb 17, 2014 at 4:28 PM, Bob Sneidar <bobsnei...@iotecdigital.com>wrote: > Okay that makes sense. The debugger has the script open and therefore the > delete stack command does not succeed, and the statements that come after > that go ahead and execute. It's the Delete Stack command that, when > successful seems to be FORCING the scrip to terminate. > > Bob > > > On Feb 13, 2014, at 12:26 , Peter Haworth <p...@lcsql.com> wrote: > > > I tried wrapping the delete stack command in a try/catch but no error was > > detected. > > > > I also tried checking if the stack was in the mainStacks right after > being > > deleted and it's not. > > > > I tried a wait command with various intervals right after the delete > stack, > > still same problem. > > > > As mentioned in my original post, if I step through the code in the > > debugger, everything works fine, at least most of the time. > Occasionally, > > the debugger skips over several lines of code right after the delete > stack > > command. I hate both those things! > > > > Pete > > lcSQL Software <http://www.lcsql.com> > > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and > > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> > > > > > > On Thu, Feb 13, 2014 at 9:29 AM, J. Landman Gay < > jac...@hyperactivesw.com>wrote: > > > >> On 2/13/14, 11:17 AM, Peter Haworth wrote: > >> > >>> I set destroyStack to true immediately before the delete stack command. > >>> Although according to the dictionary, delete stack removes a stack from > >>> memory if it's a main stack. > >>> > >> > >> The "delete stack" command should remove it from memory regardless of > the > >> destroystack setting. I do that all the time from the message box. > >> > >> But the stack won't go away if there are any pending processes. Pending > >> messages, open drivers (that's for apps usually,) handlers still > running, > >> or any other process still in progress will abort the closure. > >> > >> -- > >> 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 > >> > > _______________________________________________ > > 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 > _______________________________________________ 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
