From: "Drew Adams" <drew.adams@oracle.com>
Cc: Alex Schroeder <alex@emacswiki.org>,
Luc Teirlinck <teirllm@dms.auburn.edu>,
emacs-devel@gnu.org
Subject: RE: when to bind *down-mouse* vs *mouse*?
Date: Wed, 8 Dec 2004 12:42:45 -0800 [thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBKEFMCKAA.drew.adams@oracle.com> (raw)
In-Reply-To: <jwv4qiw37b1.fsf-monnier+emacs@gnu.org>
> 3. opening popup menus - bind down-mouse* (to work correctly
on problem
> platforms, as mentioned above)
It's not "(to work correctly on problem platforms)".
It's because we actively want to support the possibility of doing
press-button move-to-menu-entry release-button
in addition to
click-button move-to-menu-entry click-button
AFAIK, allowing both behaviors is standard in 99% of the
toolkits nowadays.
I take that as an endorsement of guideline #3, with an amendment to the
rationale.
What about other people? What about other guidelines? What about documenting
this for users?
- Drew
next prev parent reply other threads:[~2004-12-08 20:42 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
2004-12-08 19:06 ` Drew Adams
2004-12-08 19:45 ` Stefan Monnier
2004-12-08 20:42 ` Drew Adams [this message]
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=FDELKNEBLPKKDCEBEJCBKEFMCKAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=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).