DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature This is meant to work on all systems, including those that might normally use advanced input methods (although I can't say we have a heavy userbase of those ATM). The use case is programs interested in the physical key presses. In my case that's a thin client software. For users that need advanced input, they would be using this FLTK client locally and the advanced input method on the server. So the widget presenting the remote interface just want keys, whilst if I pop up some kind of local input dialog then I want the "normal" way of things. Since the land of keyboards are so poorly standardised, we also need some basic symbol information to make things behave sanely. Hence the need for resolving things like dead keys and not just trying to use the key codes. I'd say the method I've found on OS X and Win32 is rather elegant in that it gives a clear visual feedback in the OS that this application is disabling the advanced input methods. It should also be a stable method as Apple are using it themselves in Safari. Testing is of course crucial. So far I haven't had to break the ABI though, so it doesn't have to hold up 1.3.0. And I can always have a compile time test for this in our code until it gets merged. Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
