ReleaseStack message

[Richard Gaskin]

Jan Schenkel wrote:
> While this doesn't give me a direct solution for figuring it out from the 'releaseStack' message handler, it is definitely good to know about 4W_FlightRecorder!
> I think I'll suggest that my customer downloads it and uses it in combination with my warning message to debug the problem he's experiencing.
> Hopefully we'll then find the sneaky script that issues a 'stop using' behind our backs :-)

I'm glad you like Flight Recorder, but there may be a simpler way to 
resolve this without putting that into a user's hands.

How many scripts do you have running in that environment which you 
didn't write?

And is it possible something is opening the stack and then closing it, 
with your stack's destroyStack property set?

Oddly, destroyStack takes precedence over "start using", so sometimes 
simply closing a stack will remove it from the stacksInUse.

--
  Richard Gaskin
  Fourth World
  LiveCode training and consulting: http://www.fourthworld.com
  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
  LiveCode Journal blog: http://LiveCodejournal.com/blog.irv