>  > 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.
Thanks for letting me know.

>  > > Are lost events on exit an issue? I mean, if it's closing anyway...
>  >
>  > They're events I don't care about, but the fact that I'm losing them
>  > and don't know why is worrisome.
>
>  Yes. It's probably nothing, but...
>  How do you know you have lost these events, BTW?
>  Is it some sort of race thing, where you *do* get the events, but then
>  send a printf to stderr (say), and the stdio goes away (because your app
>  is exiting) before the io gets out...?

Turns out since the windows are recording the events, when I close the
window it gets deleted before I can suck the unfocus and hide events
out of the window... no big deal.

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.

>  > Writing uncrashable c++ is my main plan.  Automatically saving
>  > frequently is plan B in case the unthinkable happens.
>  >
>  > ... which is also why I turned exceptions on, so that the assert
>  > failures and range-checked accesses can be caught.
>
>  Fltk generally builds without exception support by default (it wasn't
>  widely and reliably supported in the early days) so that might prove
>  "interesting".

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?

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to