Problems with delete stack

[Peter Haworth]

After inserting some put statements at various points in my code, it's
clear that nothing in my script is being executed after the delete stack
command when run normally.  When run by stepping through the code in debug,
everything works.

I have also found that locking messages before the delete stack and
unlocking them after the open command makes things work correctly, but
that's not really a viable option since it stops any (pre)open handlers
executing on open.

Can anyone provide any insight into this very strange situation?




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 12:26 PM, Peter Haworth <pete at 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 <jacque at 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         |     jacque at hyperactivesw.com
>> HyperActive Software           |     http://www.hyperactivesw.com
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>