Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken?

2008-09-29 Thread MacArthur, Ian (SELEX GALILEO, UK)
Here's my 2 cents for helping to isolate from where it may come: 0. go to system prefs/users and check in the Startup/Open thumbnail that you don't have any booting software starting when you open a session. None. If you have any external usb or firewire controller device unplug it for

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken

2008-09-29 Thread matthiasm
On 27.09.2008, at 19:23, imacarthur wrote: Has somebody modified the keyboard handling in Fl_mac.cxx ? It seems to be broken currently. Yes, I did. The implementation is not complete yet and fails below some(?) OS version. The advantage of my keyboard function will be an advanced

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken?

2008-09-28 Thread imacarthur
On 28 Sep 2008, at 2:36, Greg Ercolano wrote: imacarthur wrote: In both cases I svn up to latest, then did a make distclean, followed by ./configure --enable-quartz --enable-threads, then a make. Seems pretty reproducible. Editing the #if 0 block (around line 1290) to #if 1 to restore

[fltk.development] fltk-1.3, OSX port keyboard handling broken

2008-09-27 Thread imacarthur
All, Has somebody modified the keyboard handling in Fl_mac.cxx ? It seems to be broken currently. Running fluid, if I try and type anything in a text entry box, nothing appears. At the console I'm getting streams of UCKeyTranslate failed: -50 messages (lacking a \n, BTW) which seems to

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken

2008-09-27 Thread Fabien Costantini
Has somebody modified the keyboard handling in Fl_mac.cxx ? It seems to be broken currently. Running fluid, if I try and type anything in a text entry box, nothing appears. At the console I'm getting streams of UCKeyTranslate failed: -50 messages (lacking a \n, BTW) which seems to come from

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken?

2008-09-27 Thread imacarthur
On 27 Sep 2008, at 19:32, Fabien Costantini wrote: Running fluid, if I try and type anything in a text entry box, nothing appears. At the console I'm getting streams of UCKeyTranslate failed: -50 messages (lacking a \n, BTW) which seems to come from line 1190 of Fl_mac.cxx. Hi Ian, I just

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken?

2008-09-27 Thread imacarthur
So I may have missed smtg in your test case showing the bug in fluid ? What do you do exactly to get the keyboard not responding ? I can get it like this. Running from a shell (so we can see the warnings!) start fluid. Then do: New Code Function/Method Select the Name(args) box and hit

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken?

2008-09-27 Thread imacarthur
On 27 Sep 2008, at 20:11, Fabien Costantini wrote: I just tested on my other 10.4.11 mac os x x86, British, Xcode 2.5, gcc 4.0.1 and it seems to work for me. Xcode 2.4.1 sorry, but I doubt it could make a difference anyway . I wonder - it might. There are compiler changes and SDK changes

Re: [fltk.development] fltk-1.3, OSX port keyboard handling broken?

2008-09-27 Thread Greg Ercolano
imacarthur wrote: In both cases I svn up to latest, then did a make distclean, followed by ./configure --enable-quartz --enable-threads, then a make. Seems pretty reproducible. Editing the #if 0 block (around line 1290) to #if 1 to restore the previous behaviour has got me up and