DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2366 Version: 1.3-current Hi! I looked into this and it seems to me that the described behavior results from different keycodes being generated for FL_KEYUP and FL_KEYDOWN events. This can also be observed with test/keyboard. I am no XIM-expert, but looking at fl_handle in Fl_x.cxx (below "case KeyPress:") I would speculate that something like keysym = XKeycodeToKeysym(fl_display, keycode, 0); is missing in the if (fl_xim_ic){ ... } block. Indeed, uncommenting "} else {" in line 1145 does the job. I even think that the test for "!filtered" is unnecessary after all, since filtered is always false at this point (?? not sure, but see lines 858-861). BTW, this ad-hoc "patch" also cures STR #2207. Maybe there is some relation to STR #2344 as well. PS: I am having fltk-1.3.x-r7626 and SuSE 11.1 here. Link: http://www.fltk.org/str.php?L2366 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
