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 Currently dead keys are pretty much hidden away from applications. For most, they don't care and this is just fine. Unfortunately I need to know when these keys are pressed for my application, and since FLTK controls the low level event handling, that means FLTK needs to be improved. I've composed a bunch of patches that fixes this for all three platforms. Existing applications should be unaffected, but applications that want information about dead keys get some new API functions that can examine the current state and what the current symbol is for each event. The patches also fixes some bugs in the same code. For X11 it returned a bogus key code for composed characters, and OS X generally had a bad connection between key presses and key events. These patches are fairly large given this somewhat obscure use case, but I still urge you to seriously consider them. The primary reason being that it's impossible for the application to do this without the help of FLTK, as FLTK controls the event loop. Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
