Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: XIM, kinput2 & Tk
- To: tlug@example.com
- Subject: Re: XIM, kinput2 & Tk
- From: jwb@example.com (Jim Breen)
- Date: Thu, 12 Apr 2001 10:17:44 +0900 (JST)
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <PCnA-.A.YkH.BJQ16@example.com>
- Resent-Sender: tlug-request@example.com
>> From: Christopher SEKIYA <wileyc@example.com> >> On Wed, Apr 11, 2001 at 05:36:37PM +0900, Jim Breen wrote: >> > Now working from what Stephen wrote above, kinput2 or whatever must be >> > active and grabbing all keystrokes to trap any initiation sequences, etc. >> > before passing them to whichever app they are intended for. >> >> Wrong sequence. It goes like this (for XIM, which I'm really growing to hate): >> >> * application creates a callback via XOpenIM() >> * Xserver receives a key sequence indicating a request for input method >> intervention Where are these keystrokes defined? Stephen said the app was unaware of them. How does Xserver know whether they are Shift+space, Ctrl+/ or whatever? I can't see a reference to them on the XOpenIM man page. >> * Xserver pipes keystrokes through input method specified by the callback >> >> (yes, that's a bit of a simplification -- Steve will set me straight if it's >> too simple) Quite clear, and therefore runs the risk of being wrong 8-)} Jim -- Jim Breen [jwb@example.com http://www.csse.monash.edu.au/~jwb/] Visiting Professor, Institute for the Study of Languages and Cultures of Asia and Africa, Tokyo University of Foreign Studies, Japan +81 3 5974 3880 [$B%8%`!&%V%j!<%s(B@$BEl5~30Bg(B]
- Follow-Ups:
- Re: XIM, kinput2 & Tk
- From: Christopher SEKIYA <wileyc@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: XIM, kinput2 & Tk
- Next by Date: Re: XIM, kinput2 & Tk
- Prev by thread: Re: XIM, kinput2 & Tk
- Next by thread: Re: XIM, kinput2 & Tk
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links