unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: 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 13:18:56 -0400	[thread overview]
Message-ID: <E1GKI64-0000Hm-J1@fencepost.gnu.org> (raw)
In-Reply-To: <44FBEEFC.3040205@gmx.at> (message from martin rudalics on Mon, 04 Sep 2006 11:16:44 +0200)

     > The right fix, in my opinion, would be lazy focus
     > change: only when a keyboard or mouse event occurs in the new window,
     > is the focus changed.  That has the disadvantage that the user may be
     > surprised by the change since the old window appears to have focus
     > before typing a key.

    That could be added.  But it would violate the principle of least
    surprise.  In my experience, the `mode-line-inactive' face and the
    `cursor-in-non-selected-windows' option handle feedback pretty well.

I really dislike that approach.

     > In order to mitigate the surprise, it might be reasonable to visibly
     > unfocus the old window (by the different highlighting of the mode line
     > and the different cursor type), but not refocus a different window
     > before an event occurs.

    That would be disconcerting, IMHO.

Also, I don't see how it would help.

     > A more radical approach would be to move toolbar and menubar just
     > above the currently selected window.  This would also require less
     > mouse movement, but would likely earn us an award for the most weird
     > user interface look ever.

    I recall someone proposing the use of popup menus instead.  There's also
    the possibility to access the menubar via F10 or the ALT key.  However,
    clients of `mouse-autoselect-window' are probably inclined to access the
    menubar with the mouse too.

We can't consider making such complex changes now, and I think they
would be really hard, so I doubt we should consider them later either.

    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.

I want to proceed with this approach, so I ask
people to study this patch in detail.

  parent reply	other threads:[~2006-09-04 17:18 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
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 [this message]
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=E1GKI64-0000Hm-J1@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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).