>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> One glaring difference is this in LyXLookupString: if (xic) {
Angus> #if 1 // somehow it is necessary to do the lookup. Why? (JMarc)
Angus> XLookupString(&event->xkey, buffer_return, bytes_buffer,
Angus> keysym_return, 0);
Angus> Did you ever get to the bottom of why you had to call
Angus> XLookupString in order to call XmbLookupString successfully?
Angus> Should xforms' call to XmbLookupString be "initialised" in this
Angus> way also?
I do not really remember why this is necessary. Looking at changes in
version 1.19 of lyxlookup.C, it seems that it was needed to make
isDeadEvent work correctly. But my memory is very fuzzy on these
things. Maybe Lars remembers...
>> The cjk-lyx problem is different, since the patch normally modifies
>> lyxlookup.C to do different stuff (actually adds a LyXIM object),
>> as can be seen here
>> ftp://stone.phys.pusan.ac.kr/pub/CJK-LyX/CJK-LyX-1.2.1-patch
>>
>> However, with xforms 1.0, this is not possible anymore afaik.
Angus> Ummmm. I still don't see why. xforms passes the raw XEvents to
Angus> the workarea handler. These are then used by LyXLookupString,
Angus> modified or not. It really shouldn't matter if xforms itself
Angus> has tried to lookup the XEvent.
I don't know really. You should ask cghan about it. He is the one who
said it was not possible.
JMarc
