Hello all - Here's an email exchange I juste had with Greg about his
Fl_Native_File_Chooser class.
Any ideas?
Christophe
-------- Original Message --------
Subject: Re: Fl_Native_File_Chooser
Date: Mon, 07 Jan 2008 13:59:21 -0800
From: Greg Ercolano <[EMAIL PROTECTED]>
To: Christophe Geuzaine <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Christophe Geuzaine wrote:
> Hello Greg - A little question about your native file chooser (version
> 0.84) on Mac OS X 10.5 (Leopard), with the latest FLTK 1.1 snapshot.
>
> If I add a shortcut in your simple-app.cxx example on line 68, i.e.,
>
> but->shortcut(FL_META+'o');
>
> then, after pressing Command+o and selecting "Cancel" in the file
> chooser, somehow FLTK still seems to think that FL_META is pressed (so
> just pressing 'o' will reopen the file chooser).
>
> I discovered this while evaluating your native file chooser for
> inclusion in my code ('Command+o' opened the file browser; after closing
> it, hitting 'q' activated the 'Command+q' shortcut for quitting the app!).
>
> Could you give this a try on your machine and check if it's an issue
> with Leopard (unfortunately I don't have Tiger around anymore...), or
> with Fl_Native_File_Chooser per se?
Hi Christophe,
Hmm, it sounds like the keyup event is being eaten by the
native operating system's file chooser, and thus the up event
never makes it to FLTK, which will continue to think the
button is down.
Not sure what to do about this offhand, since the OS's file chooser
has its own event loop that is sure to usurp FLTK's event loop.
Can you forward this to fltk.general group along with my above comments?
It's possible there's a way to tell FLTK to release the key by
forcing a key release event, to prevent the problem you're describing,
but I don't know what the correct way would be offhand.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk