> > If I just let them stay in memory and then try opening them with
>> 'modeless', I get the purge message I was having trouble with. How
>> do I open a stack that may be in memory already or may not have been
>> opened yet in a way such that I don't get the 'purge' dialog
>> appearing? Is the trick to close them in some special way, i.e. not
>> by the user simply clicking on the close window box?
>
>There's something else going on here: you should never get that dialog
>if you just reopen the same stack, regardless of whether it is
>retained in memory or not. When you *do* get it is when you try to
>open a stack that has the same name but a different file name. The
>most likely cause of this is using two different paths to get to the
>stack (are you changing the directory property at any point?), but
>setting the fileName property of the stack can also cause it, as can
>downloading a stack via HTTP and then using "save as" to save it to
>disk.
> Regards,
> Scott
Found the problem - in one case I was using a relative path and the
other I was using an absolute path. Even though both boiled down to
the same thing, using them with the modeless command triggered the
purge dialog. Once I made sure that all references were converted
into absolute paths (by converting any relative to absolute at
run-time), the problem went away.
Once again, you were right Scott!
Cheers
Peter
--
--------------------------------------------------------
Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)870 052 7576
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
