[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Re: patch for xf86-input-keyboard
From:       Daniel Stone <daniel () fooishbar ! org>
Date:       2007-11-30 19:00:41
Message-ID: 20071130190041.GH6534 () fooishbar ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tue, Jun 12, 2007 at 03:29:47PM +0300, Timo Aaltonen wrote:
> On Tue, 12 Jun 2007, Daniel Stone wrote:
> > On Tue, Jun 12, 2007 at 12:33:02PM +0300, Timo Aaltonen wrote:
> >> On Fri, 4 May 2007, Timo Aaltonen wrote:
> >>>  There's a patch that has been in Ubuntu for a year now, and I wonder if the
> >>> problem could be fixed otherwise so it could get upstream. Patch is attached,
> >>> here is the reasoning:
> >>>
> >>>  * Let keycodes 209 and 210 pass through; they're Hangul and Hangul_Hanja
> >>>    keys, needed for Korean keyboards to function correctly.  This fix is
> >>>    mostly a band-aid since XKB doesn't have a way to specify that "this
> >>>    key doesn't give you keydown and keyup events"
> >
> > Actually, I think you can specify that there's a permanent locking
> > physical behaviour.  Buggered if I can remember how, though. :)
> 
> Ok, let me know when you remember :)

Yeesh, I've been failing pretty hideously at replying to this one.  The
answer, FWIW, appears to just be putting 'permanent = yes' or such in
the key definition (e.g. key <FOO> { [ meh, blah ] permanent = yes }; or
so).

Cheers,
Daniel

["signature.asc" (application/pgp-signature)]

_______________________________________________
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

[prev in list] [next in list] [prev in thread] [next in thread]