Re: [fltk.bugs] [MOD] STR #2587: Compose not properly reset with compose_reset() on X11
[STR Closed w/Resolution] Link: http://www.fltk.org/str.php?L2587 Version: 1.3.0 Fix Version: 1.3.0 (r8522) Fixed in Subversion repository. Replacing Xutf8ResetIC() by XmbResetIC() in your patch does the same and adds no new dependency. Thanks for the patch. Link: http://www.fltk.org/str.php?L2587 Version: 1.3.0 Fix Version: 1.3.0 (r8522) ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
Re: [fltk.bugs] [MOD] STR #2587: Compose not properly reset with compose_reset() on X11
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current That may be the case, but most is the key word here. If you look at the input handling in Fl_x.cxx you'll see that they are used even outside Xft specific code. So to reiterate, this code adds no new dependencies. Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
Re: [fltk.bugs] [MOD] STR #2587: Compose not properly reset with compose_reset() on X11
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current Though most of those added functions are only used if XFT is enabled in the build (admittedly the default in 1.3) but the build can still be done in a non-XFT way for platforms that do not support the newer fuctions, or for users who do not wnat XFT. So whatever we come up with, has to work in either X11 variant, both with XFT and with only old-style Xlib support. Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
Re: [fltk.bugs] [MOD] STR #2587: Compose not properly reset with compose_reset() on X11
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current It most certainly is not behaving correctly. The documentation for compose_reset() only says If the user moves the cursor, be sure to call Fl::compose_reset().. Unfortunately it doesn't say why, but I have to assume it is so that a compose started in one input box won't continue in another, or continue when you've clicked somewhere else in the same input field. This does not work! Pressing dead diaresis in one input field, moving to another and then pressing o will give you ö. It should give you a plain o. Compare FLTK with GTK and you'll see the difference. As for the whole extension thing, FLTK already assumes those extensions are in place as all the fancy X11 input handling uses the UTF-8 functions. Check the man page for Xutf8LookupString() and you'll see the same warning. Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
Re: [fltk.bugs] [MOD] STR #2587: Compose not properly reset with compose_reset() on X11
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current In my hands, character composition seems to work correctly under Xlib so I don't see why a patch is needed. Fl::compose_reset() is now useless under Xlib because Fl::compose_state remains equal to 0 forever. Also, use of Xutf8ResetIC may not be portable because of: The function Xutf8ResetIC is an extension introduced by The XFree86 Project, Inc. in their 4.0.2 release. Its presence is indicated by the macro X_HAVE_UTF8_STRING. Could you, please, detail why you think a patch may be needed here. Link: http://www.fltk.org/str.php?L2587 Version: 1.3-current ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
