From: liyu <liyu@ccoss.com.cn>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
Peter <peter@maubp.freeserve.co.uk>,
The Doctor <thedoctor@tardis.homelinux.org>
Subject: Re: [PATCH 1/3] usbhid: Driver for microsoft natural ergonomic keyboard 4000
Date: Mon, 31 Jul 2006 08:48:44 +0800 [thread overview]
Message-ID: <44CD536C.3050703@ccoss.com.cn> (raw)
In-Reply-To: <20060728135428.GC4623@ucw.cz>
Pavel Machek Wrote:
> Hi!
>
>
>> This new version get some improvements:
>>
>> 2. Support left paren key "(", right paren key ")", equal key "=" on
>> right-top keypad. In fact, this keyboard generate KEYPAD_XXX usage code
>> for them, but I find many applications can not handle them on default
>> configuration, especially X.org. To get the most best usability, I use a
>> bit magic here: map them to "Shift+9" and "Shift+0".
>>
>
> That is hardly 'improvement'. 'X is broken, so lets break input, too'.
>
>
>
>
Well, however, this can work truly. If we do not hack as this way.
Many applications can not get its input. I think the usability for
most people should be first, but not follow rules.
I think we can add one module parameter like "shift_hack" to switch it ?!
next prev parent reply other threads:[~2006-07-31 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 10:42 [PATCH 1/3] usbhid: Driver for microsoft natural ergonomic keyboard 4000 liyu
2006-07-26 16:12 ` Josef Sipek
2006-07-27 0:47 ` liyu
2006-07-27 1:46 ` Josef Sipek
2006-07-28 13:54 ` Pavel Machek
2006-07-31 0:48 ` liyu [this message]
2006-07-31 1:30 ` Dmitry Torokhov
2006-07-31 5:24 ` liyu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44CD536C.3050703@ccoss.com.cn \
--to=liyu@ccoss.com.cn \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=peter@maubp.freeserve.co.uk \
--cc=thedoctor@tardis.homelinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.