pete at lcsql.com
Wed Jun 27 16:13:21 CDT 2012
- 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.
lcSQL Software <http://www.lcsql.com>
On Wed, Jun 27, 2012 at 12:41 PM, Mark Schonewille <
m.schonewille at economy-x-talk.com> wrote:
> 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
> Economy-x-Talk Consulting and Software Engineering
> Homepage: http://economy-x-talk.com
> Twitter: http://twitter.com/xtalkprogrammer
> KvK: 50277553
> Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab and other colour
> spaces. http://www.color-converter.com
> On 27 jun 2012, at 21:37, Peter Haworth wrote:
> > Hi Mark,
> > executing the message box command you gave me retruns true, so the stack
> > definitly still in memory.
> > The stack does have substacks and I close them all in a repeat loop
> > 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.
> > Pete
> > lcSQL Software <http://www.lcsql.com>
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode