|
I've built kinput2-v3.1 and am using the Canna36
backend.
Modified my text widget to call XOpenIM and
XCreateIC with
input method set to use callbacks for
everything. It all works
until you do the following..
shift-space to activate
IME
enter "nihongo". Hit space
and it converts to kanji
hit space again to get list of
alternates
pick one
From this point on, key events are not getting
processed
correctly any more. Instead of going to my
PreeditDraw
callback, they're going directly to my own event
handler.
Running kinput2 with -trace (compiled for
debugging) you
get
** XIM_ERROR
message received:
input-method ID: 7
input-context
ID: N/A
error code: BadProtocol
error message:
It then gets this same error for every keypress.
You can
tell that kinput is still getting the events
because if you
type "yama" and hit space twice, it pops up a
Canidate
Selection window with different forms of the word
"yama"
Also at this point, if you try to open another
window which
allocates a 2nd IC, XCreateIC returns
NULL.
Everything was built with gcc-3.1 running on Mac OS
10
with R6 libraries running XDarwin and
OroborOSX.
-- Dave Williss
------ Meddle not in the affairs of dragons, for you are crunchy and taste good with catsup |
- Re: [I18n]Problem with kinput2 Dave Williss
- Re: [I18n]Problem with kinput2 Dave Williss
