public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Petr Kocmid <Petr.Kocmid@project-bhairava.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: keys that don't create keycodes
Date: Tue, 19 Jul 2005 17:31:13 +0200	[thread overview]
Message-ID: <200507191731.13360.Petr.Kocmid@project-bhairava.org> (raw)
In-Reply-To: <1121756165.22274.50.camel@orpheus>

On Tuesday 19 of July 2005 08:56, Iain Buchanan wrote:
> It seems that every multimedia keyboard out there (especially the usb
> ones) have some or all "extra" keys that just aren't visible outside of
> Winblows.
>
> I have a couple of them!  I've tried all the usual ways of detecting
> them - xev and others that do a similar thing but they just don't
> register as keypresses in any standard way.
>
> I would like comments on why, and what methods, if any, may be available
> to detect such keys.  Surely with the plethora of cheap multimedia
> keyboards out there, there is some way.

In X, once you analyze scan codes generated by those keys with xev, you can 
assign keycodes locally wih xmodmap. In keyboard maps, you can reuse some 
exotic Fn key names available from historical mainframe terminals, unused on 
PC platform, such as F26 and Shift+F26 and so, I can't now remember the exact 
number limit for function key names, depends on how x libraries built. Works 
great for KDE, which recognizes these names well for shortcuts.

Petr
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-19 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  6:56 [gentoo-user] OT: keys that don't create keycodes Iain Buchanan
2005-07-19 15:31 ` Petr Kocmid [this message]
2005-07-19 19:09   ` Patrick Börjesson
2005-07-20  2:41 ` Sami Samhuri
2005-07-27 23:43   ` Iain Buchanan
2005-07-27  7:47 ` Robert Svoboda
2005-07-27 23:46   ` Iain Buchanan

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=200507191731.13360.Petr.Kocmid@project-bhairava.org \
    --to=petr.kocmid@project-bhairava.org \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox