> I removed about 90% of the X11 specific FLTK keyboard handling in Carbon a > while ago. Assuming that the Cocoa version builds on it, we should still be > letting OS X handle a lot of the keyboard input. I type a lot of German on my > US keyboard and getting Umlauts works as it does on all OS X native apps > (Alt-u, vowel).
It looks like the remaining keyboard code in Fl_cocoa.mm is compose stuff. From what Manolo says, this is because we can't use the native functionality without either adding a lot of hair to Fl_Input or simply swapping it out for a native input widget. So in the short term it looks like fltk gets by with its own implementation, because using the OS one is too much work. Entering Chinese with a character palette is not really practical, it would be much easier to just write in another app and then paste it into the fltk text input. This works but isn't ideal, so in the medium to long term, it would be nice to use the native input widget, which would also provide a usable Fl_Text_Display. Maybe a 1.4 thing. My own app can put off chinese input for a while, perhaps forever, so I won't be motivated to look into it seriously for a while yet. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
