all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, Luc Teirlinck <teirllm@dms.auburn.edu>,
	Drew Adams <drew.adams@oracle.com>,
	Alex Schroeder <alex@emacswiki.org>
Subject: Re: when to bind *down-mouse* vs *mouse*?
Date: Sat, 4 Dec 2004 22:42:16 +0100	[thread overview]
Message-ID: <5E007C96-463D-11D9-BA85-000D93505B76@swipnet.se> (raw)
In-Reply-To: <002501c4da35$1591b910$0200a8c0@sedrcw11488>


>
>> When the action creates a popup menu, I think we want to bind it to
>> the mouse-down event.  I seem to situations where the menu would
>> disappear as soon as you released the mouse.  If you released the
>> mouse on a menu item, that menu item has been "chosen" by the user.
>
> I do not agree on this. The reason we do not agree is perhaps that I am
> using MS Windows and you are not (I do not know what you are using)? 
> On MS
> Windows I believe it is standard that CLICKING mouse 2 brings up a 
> popup
> menu (if there is any). You can then use the keyboard or the mouse to 
> choose
> from this menu.
>
> My impression of this "standard" is that it is good because you do not 
> have
> to use the mouse very much, which can be difficult for some people and 
> for
> some other is an unnecessary burden and a hazard. I believe that this 
> could
> be a reason for the choice MS has made here.

FWIW, the standard behaviour for X toolkits is that if the mouse down, 
mouse up happens within a certain time, the menu stays up and you can 
navigate it with keys and/or mouse.  That way you get the best of both 
behaviours.

	Jan D.

  reply	other threads:[~2004-12-04 21:42 UTC|newest]

Thread overview: 25+ 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. [this message]
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
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
     [not found] <mailman.2011.1101668442.27204.help-gnu-emacs@gnu.org>
2004-11-29 15:11 ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2004-11-28 18:50 Drew Adams

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=5E007C96-463D-11D9-BA85-000D93505B76@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=alex@emacswiki.org \
    --cc=drew.adams@oracle.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.