Prima facie, I'd say that the Linux behaviour is correct as you described it.
Modal dialogs, AFAIK, should prevent all other windows in the app (and
components therein) from being activated, even if such windows were opened by
components within a modal dialog. Now, if you opened a modal dialog fro
>Um, that's what modality means - that events don't reach the
>underlying window. As you describe it, it would seem that the
>Linux behaviour is correct.
As I understood, Carl was trying to use his component *in* the modal dialog.
In that case it should work just as well as set of OK/Cancel bu
Carl H. Sayres wrote:
>
> We have a lightweight component which creates a secondary Window
> as part of it's operation. This works fine in general on Linux
> (and anywhere else as well). The problem occurs when this component
> is used in a modal dialog. On Linux, the Modal dialog blocks any
> in
We have a lightweight component which creates a secondary Window
as part of it's operation. This works fine in general on Linux
(and anywhere else as well). The problem occurs when this component
is used in a modal dialog. On Linux, the Modal dialog blocks any
input to the contents of the Window.
