Hi,
So I'm using Fl_Native_File_Chooser, and I've had absolutely no
problems with it, until possibly now. My problem may not
have anything to do with FL_Native_File_Chooser.
I've noticed that Fl_Native_File_Chooser seems to block events
in Fl_Gl_Window. I have an animation taking place in my
Next, this problem may have popped with the with 10.5.3 update.
I'm just wondering if anybody has noticed any problems with
FLTK and OpenGL because of this update.
Hmm, I was going to ask what platform you are on, and say that I find
the win32 chooser does seem to block events, but I infer
Am 11.06.08, 17:10 +0100 schrieb MacArthur, Ian (SELEX GALILEO, UK):
Next, this problem may have popped with the with 10.5.3 update.
I'm just wondering if anybody has noticed any problems with
FLTK and OpenGL because of this update.
Hmm, I was going to ask what platform you are on, and
Marc R.J. Brevoort wrote:
I have a similar situation where an add_timeout/repeat_timeout
(sometimes, not always) freezes when Fl_Native_File chooser
is open, only to happily resume after the chooser is closed
again. This happens to my program which is running on Linux.
I use a regular
Yes, but like I said its not necessarily FNFC. I've been using
FNFC for a couple years now with no problems. This OpenGL thing
seems to have only cropped up since the 10.5.3 update.
Mmm, it could be some event timing thing that 10.5.3 changed,
but may still be FNFC's fault in
On 11 Jun 2008, at 20:42, Greg Ercolano wrote:
I think my call to NavDialogRun() is the thing that blocks.
Basically this line in Fl_Native_File_Chooser_MAC.cxx:
// SHOW THE DIALOG
if ( ( err = NavDialogRun(_ref) ) != 0 ) {
..
}
..which is the thing
imacarthur wrote:
I wonder if it might be safe (on OSX) to spawn an child thread to
hold the native file chooser, and allow the main thread to continue
processing fltk events?
I wouldn't generally advocate showing new window objects from a non-
main thread, but I think it might work on
Marc - That is indeed the case on mine as well.
Greg - Well, it seems that removing the timeout
and calling redraw prior to showing the FNFC dialog
seemed to do the trick. Why this was not needed
before I'll probably never know. Sorry to scare you
with thoughts of a broken FNFC!
I wrote a
On 11 Jun 2008, at 22:13, Greg Ercolano wrote:
imacarthur wrote:
I wonder if it might be safe (on OSX) to spawn an child thread to
hold the native file chooser, and allow the main thread to continue
processing fltk events?
I think I'd considered that, but didn't like the idea for two
9 matches
Mail list logo
