[openi18n-im:01477] Re: key release issue with iiimxcf
AShiZaWa KaZuNoRi <[email protected]> Tue, 12 Jul 2005 15:26:42 +0900
| Newsgroups | gmane.comp.internationalization.input-methods |
|---|---|
| Message-ID | <[email protected]> |
Hi, Date: Tue, 12 Jul 2005 14:05:35 +0800 From: Lei Phill Zhang <[email protected]>: > > > Date: Tue, 12 Jul 2005 12:03:52 +0800 > > From: Lei Phill Zhang <[email protected]>: > > > I think iiimsf is responsible for convert the iiimp > > > event into another kind of event and send it to LE. > > > > IIIMP KEYEVENT data type does not include information like > > KeyPress or KeyRelease. So IIIMSF can not determine the > > KEYEVENT is KeyPress or KeyRelease. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > It is said that you change modifiers bit meaning to indicate the > keyPress and keyRelease. Right? Yes. This bit will be set only when the server supports the feature (not implemented yet...) > > This kind of moidification is OK I think. almost same > to define another KeyReleaseEvent (interface between LE and iiimsf, not > iiimp and iiimsf, not iiimp and iiimcf). Would you tell me how you activate KeyReleaseEvent without changing IIIMP and libiiimp.so? KeyReleaseEvent is a result of user operation on the client side, so the event must come from the client. This means that IIIMP will be involved. Am I missing something, or are you talking other features? Regards, -- kasha > > > > > > > I am not sure where is should be, but I remember I just > > > saw them near those codes who federic provides to dealing > > > the keyrelease , maybe LE.cpp. > > > > Mmm, the code by Federic caused compatibility problem in IIIMP > > and libiiimp.so... > > > > -- > > kasha