Christophe Geuzaine wrote:
> PS: clearing up the event state with
> 
> Fl::e_state = 0;
> 
> at the end of the callback fixes the problem. But this is a pretty ugly 
> hack...

        I think there might be a realtime way to check the actual
        event key states, which can then be used to resync FLTK's
        e_state value after the native OS's chooser is closed down.

        Assuming that works, I can probably incorporate that into
        the FNFC widget just after the widget is closed
        to ensure FLTK's internal key states are kept in sync with reality.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to