unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Schroeder <alex@emacswiki.org>
Cc: Luc Teirlinck <teirllm@dms.auburn.edu>, emacs-devel@gnu.org
Subject: Re: when to bind *down-mouse* vs *mouse*?
Date: Wed, 08 Dec 2004 02:38:29 +0100	[thread overview]
Message-ID: <877jnto9gq.fsf@confusibombus.emacswiki.org> (raw)
In-Reply-To: <FDELKNEBLPKKDCEBEJCBMEEHCKAA.drew.adams@oracle.com> (Drew Adams's message of "Mon, 6 Dec 2004 11:16:20 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

> And these applications nevertheless let you keep the button pressed and
> release it on a menu item to choose the item. And they let you,
> alternatively, use separate clicks: one to bring up the menu, one to choose
> each submenu (if any), and one to choose a menu item.
>
> So, I would say that it is not clear that popup menus should be opened on
> down-mouse - the reasons given so far aren't convincing. I'm not saying that
> Emacs should necessarily behave like Windows apps; I'm just asking why it is
> a good idea to bind popup menu opening to down-mouse, rather than mouse
> (mouse-up).

Assume an environment where you can press mouse-down, and a popup-menu
appears.  Keeping the mouse button pressed, move to the menu entry you
want to pick and release the mouse button.  This kind of behaviour is
possible for some systems (eg. xman for X11).  Binding a menu to
mouse-up would make this menu unusable on these systems.  The menu
won't appear unless you release the mouse, but it will disappear as
soon as you release the mouse...  That's why I think we want
mouse-down for popups.

Alex.
-- 
.O.  http://www.emacswiki.org/alex/
..O  Schroeder's fifth law:
OOO  Never accept more work than you can handle in one night of hacking.

  parent reply	other threads:[~2004-12-08  1:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 22:28 when to bind *down-mouse* vs *mouse*? Drew Adams
2004-12-03  1:10 ` Andreas Schwab
2004-12-03  1:26   ` Drew Adams
2004-12-03 10:08     ` Andreas Schwab
2004-12-03 17:22       ` Drew Adams
2004-12-03 21:22         ` Andreas Schwab
2004-12-05 14:37         ` Richard Stallman
2004-12-03  2:00 ` Luc Teirlinck
2004-12-03 17:22   ` Drew Adams
2004-12-03 18:53     ` Luc Teirlinck
2004-12-04 10:19     ` Jason Rumney
2004-12-04 17:59     ` Alex Schroeder
2004-12-04 19:06       ` Lennart Borgman
2004-12-04 21:42         ` Jan D.
2004-12-05  0:10         ` Luc Teirlinck
2004-12-07 13:20           ` Jan D.
2004-12-06 19:16       ` Drew Adams
2004-12-06 20:10         ` Stefan Monnier
2004-12-08  1:38         ` Alex Schroeder [this message]
2004-12-08 19:06           ` Drew Adams
2004-12-08 19:45             ` Stefan Monnier
2004-12-08 20:42               ` Drew Adams
2004-12-09  4:42             ` Richard Stallman

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=877jnto9gq.fsf@confusibombus.emacswiki.org \
    --to=alex@emacswiki.org \
    --cc=emacs-devel@gnu.org \
    --cc=teirllm@dms.auburn.edu \
    /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).