On 04.05.2012 14:21, Michael Baeuerle wrote: > Unfortunately I don't know how XIM works in detail, but my X server > seems to support it. The X server logfile list "XInputExtension" as > available: > ---------------------------------------------------------------------- > $ grep XInputExtension /var/log/Xorg.0.log > (II) Initializing built-in extension XInputExtension > ---------------------------------------------------------------------- > If I understand the description in [1] correctly, the IM that should be > used is selected via XOpenIM() by the client. And this function is > called from FLTK, from fl_init_xim() and fl_handle() in src/Fl_x.cxx to > name it.
[...] > It seems to me that XOpenIM() can be anything from really fast to really > slow. Therefore the interesting question is: Is it really necessary for > fltk to call XOpenIM() again every time the mouse pointer hits a new > entry on the menu bar (or a popup window is opened)? I'm intentionally only replying to this very limited aspect, because of lack of more time right now. Maybe I can take a deeper look and do my own Linux tests later... If the problem is this _repeated_ calling of XOpenIM() - well, then I have a vague recollection that this has been introduced (IIRC by Manolo) to solve a problem if the IM is not started (yet) when the program starts, or when the IM is restarted while the program runs. You should try an older FLTK version to see if this is not (such a big) problem in one of the older versions. Looking at the commit logs ... and svn blame ... okay, found it. If you have svn access, please try FLTK 1.3 before svn rev. 8097 (from Dec. 22, 2011). Is this any better? Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
