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: Christopher SEKIYA <wileyc@example.com>
- Date: Wed, 11 Apr 2001 17:55:11 +0900
- Content-Disposition: inline
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <200104110836.RAA23274@example.com>; from jwb@example.com on Wed, Apr 11, 2001 at 05:36:37PM +0900
- References: <200104110836.RAA23274@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <ku590.A.wtG.2vB16@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.2.5i-jp0
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 * 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) -- Chris
- References:
- Re: XIM, kinput2 & Tk
- From: jwb@example.com (Jim Breen)
Home | Main Index | Thread Index
- Prev by Date: Re: tar and directory information
- 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