On 7/22/11 10:26 PM, Mark Wieder wrote:
Jacque-
Friday, July 22, 2011, 7:49:28 PM, you wrote:
On 7/22/11 7:49 PM, Mark Wieder wrote:
Jacque-
Friday, July 22, 2011, 2:26:00 PM, you wrote:
You can set the destroystack property for newly-created stacks in the
Files and Memory section of prefs.
Unless you create stacks by script, in which case the destroyStack
preference is ignored... sad but true...
For real? But...I do that all the time. I guess I never actually checked
on it, but I don't remember the files hanging around in memory either.
Is that some new glitch? Does it also happen in standalones? (I wonder
how you'd check that in a standalone.)
BZ #3190 (17 October 2005), but as Mark Waddingham attempts to explain
"This isn't actually a bug."
I see. I think I agree with Mark, but in any case it doesn't affect my
code. I always script the destroystack property specifically after
creating a new stack in code, and I almost always do it in a standalone
(to make a user prefs stack usually.) It's good to know about it though.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
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
