all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
Cc: mathias.dahl@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Binding a command to the down-event of a toolbar button
Date: Sun, 02 Apr 2006 22:29:22 +0100	[thread overview]
Message-ID: <umzf3is3x.fsf@jasonrumney.net> (raw)
In-Reply-To: <E1FQ9Ku-0005U7-TJ@fencepost.gnu.org> (Richard Stallman's message of "Sun, 02 Apr 2006 16:38:12 -0400")

Richard Stallman <rms@gnu.org> writes:

>     Tool bar buttons. Many have a small arrow (triangle) to the lower
>     right to indicate that more actions are available. Methods of getting
>     to the advanced actions vary, I have seen applications where you the
>     hold down mouse-1, others where you press mouse-3, and others where
>     you click on the small arrow itself. All these methods result in a
>     drop down menu appearing.
>
> This sounds like a very special case.  The triangle is not a member
> of the tool bar, it is a special part of the tool bar mechanism itself.

The triangle is just a visual indicator to tell you that more than
just one action is available.

> In the case where you get the menu by holding down mouse-1 on the
> triangle, what happens when you just click mouse-1 there?

The "default action" for that toolbar button is executed.

As an example of how such a feature is used, the Print icon on the
Emacs tool bar currently runs print-buffer. In the above scenario, it
could drop down a menu when the mouse button was held down for more
than 1 second, offering access to print-region,
ps-print-buffer-with-faces and ps-print-region-with-faces as well.

  reply	other threads:[~2006-04-02 21:29 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26  5:10 Binding a command to the down-event of a toolbar button Stefan Monnier
2006-03-28 19:33 ` Richard Stallman
2006-03-30  9:56   ` Mathias Dahl
2006-03-30 22:39     ` Stefan Monnier
2006-03-30 23:03       ` Drew Adams
2006-03-31  7:58         ` Eli Zaretskii
2006-03-31 20:20           ` Richard Stallman
2006-04-01 11:43             ` Eli Zaretskii
2006-03-31 17:28         ` Richard Stallman
2006-03-31 18:35           ` Drew Adams
2006-04-01 11:45             ` Eli Zaretskii
2006-04-01 16:21               ` Drew Adams
2006-04-02 20:38                 ` Richard Stallman
2006-04-01 13:46             ` Richard Stallman
2006-04-01  3:12           ` M Jared Finder
2006-04-01 20:28             ` Richard Stallman
2006-04-01 20:58               ` M Jared Finder
2006-04-03  1:09                 ` Richard Stallman
2006-04-03  4:14                   ` M Jared Finder
2006-04-03 18:24                     ` Richard Stallman
2006-04-04  2:13                       ` M Jared Finder
2006-04-04 19:57                         ` Richard Stallman
2006-04-05  6:04                           ` M Jared Finder
2006-04-05 19:06                             ` Richard Stallman
2006-04-06  5:40                               ` M Jared Finder
2006-04-06 15:37                                 ` Richard Stallman
2006-03-31 10:18       ` Jason Rumney
2006-03-31 11:01         ` David Kastrup
2006-03-31 14:34         ` Stefan Monnier
2006-04-01 13:45           ` Richard Stallman
2006-04-01 16:27             ` Stefan Monnier
2006-04-01 13:45         ` Richard Stallman
2006-04-01 19:01           ` Jason Rumney
2006-04-02 20:38             ` Richard Stallman
2006-04-02 21:29               ` Jason Rumney [this message]
2006-04-03  3:24                 ` Richard Stallman
2006-03-31 17:28     ` Richard Stallman
2006-04-01  0:55       ` Kevin Rodgers
2006-04-01  1:12         ` Robert J. Chassell
2006-04-01  3:59         ` Stefan Monnier
2006-04-01 20:28           ` Richard Stallman
2006-04-03  2:01             ` Stefan Monnier
2006-04-03 13:51               ` Richard Stallman
2006-04-03 18:24                 ` Richard Stallman
2006-04-01 20:28         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=umzf3is3x.fsf@jasonrumney.net \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mathias.dahl@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.