>On 8/8/00 4:01 pm, Peter Reid <[EMAIL PROTECTED]> wrote:
>
>> Thanks Kevin. Can I just check what you mean by the above. The
>> support stacks I'm using are all in their own separate *.mc files and
>> designated as 'mainstacks', and they all have destroy stack & window
>> set.
>
>If they are mainStacks and don't have any open substacks, then just closing
>(or of course deleting!) them should do the trick.
With the 'close' command? If the user closes a stack by clicking into
the window box, it leaves the stack in the state that leads to the
purge dialog??
> > How should I close them such that they fully disappear, but can be
>> reopened at any time with either 'modeless path/stack.mc' type
>> command - or any other sensible way of opening them? I don't want to
>> save anything in these support stacks - they are used for printing
>> and displaying on-screen help. They are outside the main stacks I'm
>> developing so they can be shared between them rather than repeat them
>> within each main CBT stack.
>
>You should ask yourself if you really need to remove these stacks from
>memory at all. If you have enough and/or your needs are not that great, its
>often best to leave stacks in memory after closing so they load faster next
>time.
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?
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.
