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 Ah. Mac is still new to me, so please continue to examine those portions extra carefully. For this specific case, it seems that you can get input directly through insertText. Since this isn't a key press, I'm reluctant to present it to the application as such. I see three possible solutions here: 1) Fake a keydown (and possibly key up) using a special key code meaning "this isn't really an actual key". 2) Send the text as a FL_PASTE event. 3) Create a new event type, something like FL_TEXT. Opinions? For the next question, the X11 patch also includes the basic groundwork for this change. The second modification to Fl_compose.cxx is because the Mac code was structured a bit oddly compared to other platforms: - The input widgets rely on Fl::compose() returning false for keys that need special care. - All platforms except Mac has a test in Fl::compose() for control characters, fixing this. - For Mac, the check was instead done in the platform code and achieved the correct result by clearing out e_text. I changed the code so that Mac behaves like the other platforms by looking for control characters. To be honest, Fl::compose() probably needs a rewrite to make it cleaner. 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
