From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [rudalics@gmx.at: Re: [simon.marshall@misys.com: mouse-autoselect-window needs a de lay]]
Date: Mon, 04 Sep 2006 16:05:47 +0200 [thread overview]
Message-ID: <m3mz9fvi9w.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <44FBEEFC.3040205@gmx.at> (martin rudalics's message of "Mon\, 04 Sep 2006 11\:16\:44 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> I don't think that the delay stuff is a good strategy: it brakes and
>> confuses the user when he indeed wants to change focus, and it causes
>> hectic when he doesn't.
>
> That's what I thought before I started implementing this. Currently, I
> use a value of -0.5, that is, wait for about a second after I started
> moving the mouse and select the other window iff the mouse doesn't move
> any more. So far I didn't notice any confusion with these settings.
To me it makes more sense if this "move and stop" is the default method
(ie. selected with a positive delay value). The negative value could
be for experts which want just the move delay.
But why not separate the two timeout settings, e.g. make it a cons with
the "move delay" in the car and "stopped delay" in the cdr. That's
easy to set via customize.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-09-04 14:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 15:17 [rudalics@gmx.at: Re: [simon.marshall@misys.com: mouse-autoselect-window needs a de lay]] Richard Stallman
2006-09-03 16:02 ` David Kastrup
2006-09-03 16:37 ` David Kastrup
2006-09-04 9:16 ` martin rudalics
2006-09-04 14:05 ` Kim F. Storm [this message]
2006-09-05 9:21 ` martin rudalics
2006-09-05 11:02 ` Kim F. Storm
2006-09-05 11:06 ` David Kastrup
2006-09-05 12:53 ` martin rudalics
2006-09-05 13:12 ` David Kastrup
2006-09-05 15:59 ` martin rudalics
2006-09-04 17:18 ` Richard Stallman
2006-09-03 17:05 ` Chong Yidong
2006-09-04 9:27 ` martin rudalics
2006-09-04 14:07 ` Kim F. Storm
2006-09-03 21:43 ` Kim F. Storm
2006-09-05 15:20 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mz9fvi9w.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).