Re: Delete stack

2012-06-27 Thread J. Landman Gay
On 6/27/12 1:45 PM, Mark Schonewille wrote: The application browser is unreliable and that's why I stopped using it years ago. To check that the stack was removed from memory, you use the following syntax in the message box: Perhaps it's changed since you last used it. I leave it open all the

Re: Delete stack

2012-06-27 Thread Peter Haworth
Thanks Paul, you nailed it! I did as you suggested, except I simply closed the stack after setting destroyStack to true rather than delete it and all worked. I had to refresh the Application Browser to see it disappear but that's not unusual. Thanks to you and Mark for helping out. Pete lcSQL S

Re: Delete stack

2012-06-27 Thread Paul Hibbert
Maybe I am misunderstanding something, but if you are applying the destroyStack right before the delete stack you are not changing anything permanently, unless you save the stack before deleting it of course. Called from "Stack A": set the destroyStack of stack "Stack B" to true delete st

Re: Delete stack

2012-06-27 Thread Mark Schonewille
Hi Peter, Maybe you need to post the relevant part of your script. Also, I didn't mean to lock messages but to turn them off in the Developer menu and to do all tests from the message box. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://ec

Re: Delete stack

2012-06-27 Thread Peter Haworth
Hi Mark, - The result is empty after the delete. - I don;t refer to the long ID of the stack anywhere in my code - I locked messages right before the delete and unlocked right after: the stack was still in memory. Weird! Pete lcSQL Software On Wed, Jun 27, 2012 at 12:

Re: Delete stack

2012-06-27 Thread Mark Schonewille
Peter, Check the result. Do you have a script somewhere that uses the long id before you get a chance to check whether the stack is still in memory? What happens if you turn off messages before deleting the stack? Is it still in memory when you test for it? -- Best regards, Mark Schonewille

Re: Delete stack

2012-06-27 Thread Peter Haworth
HI Paul, Unfortunately, I can't use that method. I'm doing this as part of a tool I'll be announcing soon so it will be accessing other peoples' stacks and I don't think they'd be happy if I changed the destroyStack property on them! Pete lcSQL Software On Wed, Jun 27, 20

Re: Delete stack

2012-06-27 Thread Peter Haworth
Hi Mark, executing the message box command you gave me retruns true, so the stack is definitly still in memory. The stack does have substacks and I close them all in a repeat loop before the delete stack command, but I don;t get any error messages as you described. This is with LC 5.5.0 OSX 10.7.

Re: Delete stack

2012-06-27 Thread Paul Hibbert
Peter, Have you tried setting the destroyStack to true before deleting it? set the destroyStack of myStack to true Quote from the LC Dictionary; "destroyStack Summary: Specifies whether a stack is purged from memory when it's closed, or whether it remains in memory. Value: The destroyStack of

Re: Delete stack

2012-06-27 Thread Mark Schonewille
Hi Peter, The application browser is unreliable and that's why I stopped using it years ago. To check that the stack was removed from memory, you use the following syntax in the message box: put (there is a stack "") I think that the application browser stores the long id of a stack somewhere