> Argh! Maybe I spoke too soon... Oh, no, wait a minute, fltk-1.3 is broken too > hmm, that is odd. Oh, and also the fltk3 "native" test... > > > OK, here's the thing: On this box, if I run the fullscreen test in > "dual-window" mode, i.e. > > > ./fullscreen -2 > > then, whenever I click the "Double Buffered" button (to force the GL window > into double buffered mode) the control panel window (which is meant to be > set modal) disappears, leaving me with a GL window that I can't close (it > shrugs of ESC and close events...) > > I wonder if something is hosed on this machine?
More info: Works OK on X11, though this client is struggling a bit with the border on/off switching... Should probably have mentioned that the eralier problems were all on WinXX host. I'd likely have berated someone else for failing to mention that... Also, at least on this WinXP test box, even the fltk-1.1 tarball version of "fullscreen.exe -2" doesn't work right either, so I don't think I'm finding a new problem. Well... Anyway, it is some sort of interaction between the GL window and setting the "control" window modal() (or indeed non_modal() too) that triggers the problem. If the control window is "normal" it works fine, but of course gets lost behind the fullscreen... If I have the button callbacks explicitly show() the control window to force it to raise, and DO NOT set the control window [non_]modal() at all, then it all seems to work just fine... _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
