>> Hmm, well if that's true, isn't it all redundant and can be removed >> right now? > > I don't know. > Possibly it can be, or can be made X11 specific - if we believe the > OSX and win32 implementations cover what's needed.
Even if by some chance the fltk input has some great feature that was awkward in the native input method... no one knows its there. But I'd be real surprised if the native input methods don't cover everything needed. > I'm thinking of the case where I might be typing something in a > European language (and don't have any IME running) but need to type > some glyph that's not on my keyboard, then the fltk compose stuff > might come into play. Well, you'd do whatever it is you do for every other app on the system. Both the mac and windows have key shortcuts that switch between input methods, and anyone who switches between input methods frequently, like myself, will have those shortcuts well memorized. If you only need the occasional European glyph, well that's why even the English IME already has dead-key and compose support. AFAIK, this stuff makes sense under X where there is no system IME and every app rolls its own. Actually, I wouldn't be surprised if there weren't some kind of system level IME thing on X too nowadays, but I don't use X enough lately to know... it's probably part of one of those desktop thingies, and fltk certainly can't be fast and light if it starts off saying "first start up GNOME...". >>> I am not familiar with the Apple IME, so don't know if that works - I >>> assume that it does, though? Or are you saying that it does not? >> >> It doesn't for me... > > Hmm, OK. I think it is meant to. > How do you invoke it? Maybe I'll get a chance to look. Does Manolo You can try the steps I outlined previously, prefs -> international -> etc. >>> Hmm, CMD-A seems to work for me on this Mac (just tried a few simple >>> widgets though.) Where is it failing for you? >> >> The part where everything gets selected :) I'm on OS X 10.5.8 and I >> just tried with test/input on the latest 1.3. Cmd-a does nothing. > > Oh yes - works in my test harness, but now I try the fltk test/input > demo, I see it does nothing. > Did this used to work? I thought it used to work... It doesn't work on fltk 1.1.9 either. I think we need an edit menu. Maybe you already manually added an edit menu to your app so it works for you? _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
