public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Subject: Re: I lose characters because keycode of Fn is same than DEL
Date: Wed, 06 Jul 2011 08:16:00 -0000	[thread overview]
Message-ID: <4E130870.4010804@dronecode.org.uk> (raw)
In-Reply-To: <CAMPAy3aoJm1VxrqTFhkw5D_+6j4NgvX82Q1=eOYSBoaQaog-uA@mail.gmail.com>

On 04/07/2011 16:19, Phil Betts wrote:
> On 1 July 2011 16:13, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
>> I was aiming to generate an unused keycode, though, so I'm not sure I've
>> picked a good one.
> 
> Understood, although just about anything is preferable to Delete :)
> 
> Since Fn functions as a modifier, perhaps one of the Mod keys, e.g.
> Mod5 might be a better choice.
> 
> As long as it can be distinguished from any other key, we can use
> xmodmap to map it to whatever we want (e.g. Control_L for me).

Well, I was aiming for it to do nothing by default and then it can be mapped
to a modifier if desired.

>> Can I see the output of 'setxkbmap  -print' as well, please?
> 
> xkb_keymap {
>         xkb_keycodes  { include "xfree86+aliases(qwerty)"       };
>         xkb_types     { include "complete"      };
>         xkb_compat    { include "complete"      };
>         xkb_symbols   { include "pc+gb+inet(pc105)"     };
>         xkb_geometry  { include "pc(pc105)"     };
> };

Hm.. this is strange, I have the same keymap, but when I generate that key
event (I have to hack my X server to do that as I don't have a Fn key), I get:

KeyPress event, serial 27, synthetic NO, window 0x800001,
    root 0x101, subw 0x0, time 7868875, (90,80), root:(2056,142),
    state 0x0, keycode 93 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 27, synthetic NO, window 0x800001,
    root 0x101, subw 0x0, time 7868968, (90,80), root:(2056,142),
    state 0x0, keycode 93 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

.. and this seems right looking at the output of 'xmodmap -pk', so there's
something else going on here I don't understand :-)

> I get the same output regardless of whether X is started with or without
> an external keyboard plugged in (is the external keyboard even
> considered?).

Not really, all the Windows keyboard input (which may come from real keyboards
or programs pretending to be one) is composed into a single virtual X keyboard.

Perhaps this isn't quite right but works well enough for most purposes :-)

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      reply	other threads:[~2011-07-05 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  9:33 Paul Maier
2011-06-23 11:34 ` Jon TURNEY
2011-06-30  8:40   ` Phil Betts
2011-06-30 16:51     ` Jon TURNEY
2011-07-01 11:21       ` Phil Betts
2011-07-01 15:14         ` Jon TURNEY
2011-07-05 12:50           ` Phil Betts
2011-07-06  8:16             ` Jon TURNEY [this message]

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=4E130870.4010804@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).