Hi Richard, Sorry for the late reply - the day-job was getting in the way again...
It does look related to QCC entry 5270 <http://quality.runrev.com/show_bug.cgi?id=5270> titled "Libary closes when a substack closes" I downloaded Ken Ray's example stack, and when I add a 'releaseStack' handler to that unexpectedly unloaded library, the message isn't triggered either. But the circumstances in my case are slightly different: the library stack itself doesn't have its destroyStack property set, nor the substack that it clones. However, one of the last thing the library does, is turn on the destroystack of the fresh clone - so it could still be a manifestation of the same engine problem. Still looking for a workaround that doesn't require invisibly opening the library stack. I sent a slightly tweaked version of my library to the customer, hoping it does the trick - we'll have to wait and see. Thanks for the hint! Jan Schenkel. ===== Quartam Reports & PDF Library for LiveCode www.quartam.com ===== "As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld) ----- Original Message ----- From: Richard Gaskin <ambassa...@fourthworld.com> To: use-livecode@lists.runrev.com Cc: Sent: Monday, May 21, 2012 10:40 PM Subject: Re: ReleaseStack message 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 _______________________________________________ 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
