public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Takuma Murakami <murakami@ipl.t.u-tokyo.ac.jp>
To: cygwin-xfree@cygwin.com
Subject: Re: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22]
Date: Fri, 21 Nov 2003 09:22:00 -0000	[thread overview]
Message-ID: <20031121171819.F6E4.MURAKAMI@ipl.t.u-tokyo.ac.jp> (raw)
In-Reply-To: <3FBCF6D0.4090500@msu.edu>

It is my mistake that "silently" changing the default
behaviour.  I apologize and add some comments to show
my intention.

Harold L Hunt II wrote:
> It might be nice, but the Windows autorepeat caused problems with 
> systems running in Japanese... so they need the XKB autorepeat 
> functionality, since the Windows autorepeat needs to be disabled for them.

The Windows autorepeat is not crucial to Japanese
language handling.  Disabling it was a part of the patch
to improve mode key states synchronization.  Sorry for
confusing you, Harold.

I disabled it for the two reasons below:

1)  Having both Windows and XKB autorepeat breaks the
state synchronization.  For example, if we press Caps
Lock for a while, Windows toggles the state exactly once
but XKB repeatedly toggles the state since it receives
many KeyPress events generated by Windows autorepeat.

2)  Having two schemes for autorepeat looks not so
good as Harold said.  Adoption of XKB layer is just my
choice.  Because we are using an X server, it is natural
for me to configure it using X Window's manner (i.e.
xset).  Please consider keymaps; we set keymaps via
xmodmap, setxkbmap and/or XF86Config file -- all those
are X Window's manner.

Anyway, now we seem to find a better solution to get
default values from Windows and enable Windows autorepeat
if XKB is disabled.  It looks that Alexander is implementing
the features, is it right?  I really appreciate him.

Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp)


  parent reply	other threads:[~2003-11-21  9:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 11:10 Updated: XFree86-xserv-4.3.0-22 tulitanssi
2003-11-11 13:15 ` Harold L Hunt II
2003-11-11 16:33   ` Dr. Volker Zell
2003-11-11 16:45     ` Harold L Hunt II
2003-11-11 17:17       ` Dr. Volker Zell
2003-11-12 20:02         ` Dr. Volker Zell
2003-11-13  8:39           ` Alexander Gottwald
2003-11-13 21:47             ` Alexander Gottwald
2003-11-18 21:32               ` Zbynek Winkler
2003-11-18 21:50                 ` Harold L Hunt II
2003-11-18 22:22                   ` Zbynek Winkler
2003-11-19 14:12                 ` Alexander Gottwald
2003-11-19 18:38                   ` Alexander Gottwald
2003-11-20 17:06                   ` Jack Tanner
2003-11-20 17:16                     ` Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] Harold L Hunt II
2003-11-20 18:53                       ` Jack Tanner
2003-11-20 18:58                         ` Harold L Hunt II
2003-11-21  9:22                       ` Takuma Murakami [this message]
2003-11-12  8:55 ` Updated: XFree86-xserv-4.3.0-22 Takuma Murakami
2003-11-20 20:35 Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] Cary Jamison
2003-11-20 20:46 ` Harold L Hunt II
2003-11-21  8:29   ` Zbynek Winkler
2003-11-21 14:30 ` Alexander Gottwald

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=20031121171819.F6E4.MURAKAMI@ipl.t.u-tokyo.ac.jp \
    --to=murakami@ipl.t.u-tokyo.ac.jp \
    --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).