I certainly wouldn't cry if that happened, although now i use the
same device to put a stack into memory. I admit it is a "back handed"
way to do things, tho.
Best,
Jerry Daniels
Makers of Galaxy 1.5
http://www.daniels-mara.com/new_in_galaxy_1_5.htm
On Oct 31, 2006, at 9:59 AM, Richard Gaskin wrote:
Jerry Daniels wrote:
Any reference to any object in a stack (or the stack itself) that
includes its file path name (the long name, the long id) will
place it in memory. You might consider that. We had that bite us
several times with Constellation and Galaxy in managing our tabs
for objects.
That this would be the case with stacks whose destroyStack property
is FALSE makes sense, but when a stack's destroyStack is TRUE this
is inconsistent with other behaviors we've come to expect from the
engine.
Given that this has caused confusion for yourself, Jacque, Ken,
myself, and other experienced Rev programmers, it seems reasonable
to request that the destroyStack property be honored consistently,
which I've done in BZ#3937:
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=3937>
--
Richard Gaskin
Fourth World Media Corporation
___________________________________________________________
[EMAIL PROTECTED] http://www.FourthWorld.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
