Thank you for fixing it so quickly!Yes, the restart problem doesn't matter.
"it seems that other applications (e.g., xterm, the gnome terminal) react very badly to xim server stop and restart." Do you mean when xim is killed by "kill -9", the terminal exec "killall -9" will freeze sometimes? And if the frozen terminal was killed by xkill , sometimes the terminal will not exit and use near 100% CPU. I am not sure what happened, so I test the restart in a split terminal with rxvt & or gnome-terminal & wihtout frozen the original terminal. And kill the frozen terminal in the original terminal if need. If the frozen terminal and xim were killed completely , gnome-terminal can input with xim after the xim start again. I haven't met other problems except the frozen problem. For xterm, there are some problems with the fonts, locale encoding, or more. At least, it does not support fcitx completely. For rxvt, multichar_encoding must be set to Big5 to support gbk encoding. If rxvt was configured, it works as well as gnome-terminal for the fcitx restarting. > > [STR Closed w/Resolution] > > Link: http://www.fltk.org/str.php?L2474 > Version: 1.3-current > Fix Version: 1.3.0 (r8097) > > > Fixed in Subversion repository. > > Only part of the STR is fixed really, that where the xim server > starts after the FLTK application. X input now runs well in this > situation. The other part, where the xim server is killed and restarted > while the application runs is not fixed. However, while the first > part corresponds to a practical need (run an FLTK application > at X startup: it can start before the xim server is ready), > the second part seems theoretical. Furthermore, it seems that > other applications (e.g., xterm, the gnome terminal) react very > badly to xim server stop and restart. > > > Link: http://www.fltk.org/str.php?L2474 > Version: 1.3-current > Fix Version: 1.3.0 (r8097) > _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
