[openi18n-im:01444] Re: key release issue with iiimxcf

Kasha,

>From LE and IM point of view, KEYEVENT data type isn't incompatibly
changed, a new member 'member' is appended at end of the original
KEYEVENT struct, those *existing* LE *binary* can work well with the new
change.

The root cause happens in client side, i already sent to alias, i just
modified iiimgcf, other client frameworks such as iiimxcf and iiimqcf
should be synced with the change as i amn't familiar with them, i hope
someone can do it, but nobody step in, but i have to hack by myself to
incompatibility issue. :(

Hope it can clarify.

-federic

> Date: Tue, 28 Jun 2005 22:01:54 +0800
> From: Federic Zhang <[email protected]>:
> > 
> > It is caused by iiimxcf, if the attached patch is patched to
> > iiimxcf/xiiimp.so/iiimp/KeyMap.c, it should work.
> 
> I think I understand the root cause.  The implementation of key
> release feature breaks compatibility.  KEYEVENT data type is
> incompatibly changed.
> 
> So the question is that whether this feature can be implemented
> in a compatible way or not.
> 
> Federic, how do you think?
> 
> Thanks,
> -- 
> kasha