On 26 Feb 2008, at 18:37, Evan Laforge wrote: >>> Which platforms have this restriction anyway? >> >> Well, hard to say. I know I have encountered it on win32, >> although not > > Ow, well sounds like I should make main my ui thread just to eliminate > one more variable in the random "things weirdly broken" bughunt.
Yes, I'd recommend caution here - although recent X-servers are reputed to be "clean" in this respect, I don't know which are/are not. And I'm not sure about OSX. > I'm sure this is documented somewhere, but I also noticed that just > putting an event handler in the window doesn't capture all events... > when e.g. an entry has keyboard focus it seems the keydowns go > directly to it, and Fl_Window::handle never sees them. Yes, IIRC, if an input widget has the focus, it will be offered the event directly itself - only if it rejects it will the event be offered more generally... This is in the docs (somewhere) maybe in the event handling section? I don't recall... > Yeah, I had to get rid of -fno-exceptions. Tracking down this > problem, BTW, was made difficult by the way fltk's Makefile hides the > commands it's running. As soon as I commented out that .SILENT things > were much clearer. Is there a good reason to have that, or did > someone just think it would look nicer if make produced less output? I think this is very much a taste issue... I like it this way (although it was not me who created the Makefiles like that) as it makes errors and warnings more visible. Of course, I knew about commenting out the .silent so it's seems obvious to me that is what to do - less obvious to someone coming this way from cold, though... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
