On Mon, 27 Sep 1999, Hugh Senior wrote:
> Having spent more debugging time on this than I would care to confess, the
> following may be worth remembering if you meet a similar situation.
>
>
> Topic: Calling a modal from a modal
>
> This can be useful when sequential user decisions are required. However,
> in order to keep the modality all all sequentially opened stacks, the
> following points must be kept in mind...
>
> [1] Do not use "set the defaultStack"; use long syntax instead
I don't follow this. You only need to set the defaultStack if you
want the dialog to be modal from some stack other than the current
one. And using the long syntax doesn't solve this problem.
> [2] Ensure each stack opened as a modal has its "destroy stack" and
> "destroy window" properties set to TRUE in the stack properties
DestroyStack has nothing to do with behavior in this area, and since
most modals dialogs are stored as substacks anyway, it's irrelevant
(substacks aren't ever destroyed by themselves). Setting
destroyWindow to true is a good idea if there's ever a possibility
that a stack will be reopened immediately after it is closed, but only
on X11 systems (its an application/window manager synchronization
problem inherent with the design of X11). I don't know why it would
make any difference on Windows or MacOS systems.
> This should ensure your modals respond as modals and not break the
> behaviour chain.
The only ways I know of to break the modal chain is to try to open a
stack in some mode other than modal from a modal, or to open a modal
from some stack other than the modal stack when one is opened. If you
don't do either of these things, you should be OK.
Regards,
Scott
> /H
>
> Hugh Senior
> The Flexible Learning Company
> Consultant Programming
> Voice: +44 (0)1483.27 87 27
> Web: www.flexibleLearning.com
>
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
