Yuri D'Elia wrote: > In article <[EMAIL PROTECTED]>, > Albrecht Schlosser <[EMAIL PROTECTED]> > wrote: > >> BTW: in STR 1869 <http://www.fltk.org/str.php?L1869> I described >> a problem that turned out to be an interaction of Fl::grab() and >> Fl::readqueue(). The proposed patch has the (IMHO minor) side >> effect, that you can drag the window away from an open menu, when >> the fl_ask() or fl_alert() window is open. Just like someone else >> mentioned earlier (WRT OS X) in this thread. > > This behavior is broken nonetheless, don't you think?
Yes, no question, it IS broken. I'll post this to the STR later. Maybe it can be fixed by a FLTK kernel guru. > Under X11 the grab equivalent is called "override redirect", and is > indeed a mayor source of problems. If Fl::grab() can't be fixed in a cross platform way, and if it is broken anyway, then why should we leave the docs stating something that can't be done. IMHO, the docs should be fixed, and in the 1.1.8 version, there can't be other modifications, anyway. The docs should say something like: "On recent (X11) window managers, Fl::grab() can't be guaranteed to work as proposed. Thus everything that can be done is to redirect all events to one window _within_ the FLTK event dispatching, and that doesn't affect any other windows or applications running on the same desktop. For other operating systems (and MS Windows ;-) ), the same applies, resp.." > The proper way of fixing menus&company is really simple in reality: use > the proper WM support of "popup" window classes. I have some idea of how > we could do this on X11, and maybe on Carbon, but I have no experience > in this area for Windows. Better to be done for the followup version after 1.1.8 > BUT, > > 1- I'm not sure how this would play with the actual even model (ie: does > it would break the API in some way?) > 2- I'm not sure we can do that for 1.1.8 without breaking the ABI. > > While I'm not advocating the use of grab, I still would like grab and > warp pointers to be available if possible (mainly for GL programs). Yes, don't remove features that existing users may rely on, but if the window managers don't honor FLTK's requests anyhow, then why should be try to do something that can't be done reliably on different platforms? Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
