> Proposal: Add a Fl_Window::show_modal() method. I've only been using
> FLTK for about 2 months and I've already had an occasion to use this
> four times.
>
> Something along these lines...
>
> void Fl_Window::show_modal()
> {
> show();
>
> // Wait until hidden
> do { Fl::wait(1); } while (visible());
> }
Harvey,
I'm not entirely sure what you are achieving by doing this, but note
that fltk already has support for 3 types of window modality: "normal",
"modal" and "non-modal".
A "normal" window is, well, normal.
A "modal" window stays on-top and grabs all the interactions so that the
main app does not get any until the modal-window is dismissed.
A "non-modal" window stays on-top, but does not grab the interactions,
so the app still gets clicks, keyboard input (etc) that are focused to
it. If you see what I mean.
If your intent is one of these three things, then I suggest that using
the existing mechanisms is preferred.
If your intent is something different, then we can't use the word
"modal" in this context because that may be confusing with the existing
implementations - we will need to find some other descriptive word for
this mechanism.
SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
