nanogui: Problems with modal windows
Subject:
Re: [nanogui] Problems with modal windows
From:
Mark Mussetter ####@####.####
Date:
21 Dec 2004 15:10:47 +0000
Message-Id: <6.1.2.0.0.20041221080636.01b5e588@link-comm.com>
Hi Greg,
Thanks for the explanation. I'll look into nxlib and fltk and see what I
can see. I'm thinking a quick fix to get the window to show on top might
be to just call a microwindows raise event directly from program and
bypassing FLTK just for the important window. Do you see a problem with that?
Thanks for you help,
Mark
At 01:13 AM 12/19/2004, you wrote:
>: WindowA (non-modal) -- This window allows the user to adjust settings.
>: WindowB (modal) -- This window is a modal "confirmation" window. The
>: user must OK this window before moving on.
>:
>: WindowC (modal) -- This window is shown when an interrupt is fired
>: indicating that the power switch was pressed and we're shutting down.
>:
>: After the user makes changes in WindowA, WindowB is shown so the user must
>: confirm the changes before moving on. If the power switch is pressed
>: before the user confirms settings, WindowC gets shown, but it stays behind
>: WindowB. WindowC gets any further events from the touchscreen even though
>: it is shown behind WindowB.
>
>Unfortunately, this problem is likely buried in the implementation
>of FLTK itself. I would need to understand a bit more exactly
>how FLTK implents "modal" windows. Microwindows itself
>doesn't have the concept of modal windows. Modal windows
>are normally implemented by forcing a new GetNextEvent
>loop "on top" of the topmost existing window's event loop,
>thus forcing all messages to go just to it, thereby implementing
>the modal concept.
>
>It sounds likely that there's some issue where FLTK isn't communicating
>fully with nano-X to get the window raised when it is shown.
>This could be an issue in NXLIB, if you're using that emulation
>library.
>
>Regards,
>
>Greg
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
