From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Toolbar redraw causes unwanted selection
Date: Tue, 19 Dec 2006 11:02:28 +0100 [thread overview]
Message-ID: <m3vek8b3uz.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <BD84C93D-F629-4A24-841B-5439FFBAD826@as.arizona.edu> (JD Smith's message of "Mon\, 18 Dec 2006 09\:14\:51 -0700")
JD Smith <jdsmith@as.arizona.edu> writes:
> On Dec 15, 2006, at 2:24 PM, Richard Stallman wrote:
>
>>> The reason I suggest waiting for C-l (or maybe for something else)
>>> before making it smaller is that I think the frequent changes
>>> in tool bar size, when switching back and forth between two windows,
>>> could be annoying for the user.
>>
>> I don't see an easy way to implement the "wait for C-l" -- and
>> for the
>> case at hand, it doesn't even solve the problem, as the abnormal
>> behaviour happens when the toolbar size is increased.
>>
>> You are right; this bug would still have to be fixed at the low level.
>>
>> Nonetheless, the change I suggest in the auto-resize behavior would
>> avoid a behavior that might be quite annoying. It only takes two
>> characters to switch windows, and I often do that a few times in a
>> row. If the toolbar were to change size each time, it would be
>> very distracting. If it were to remain enlarged until I type C-l
>> to let it shrink back down, that distraction would be gone.
>
> As someone who often switches rapidly between row and 1-row toolbar
> windows (a C buffer and an IDLWAVE buffer, for instance), I can
> confirm that the constant resizing is a bit annoying -- though much
> less than the original unintended selection.
So why don't you turn it off then?
> One toolbar size per
> frame would seem a good idea,
That's already what tool-bar-lines in frame-paramteres do.
> based on the maximum number of rows
> required for all windows in that frame. This way, as buffers are
> switched to other modes/etc., the toolbar resizes, but simply
> switching windows (by clicking, C-x o, etc.) won't trigger the resize.
That's a nice idea, but quite impractical. The tool-bar may depend on
a keymap property at specific buffer positions, so how can you know
what's needed?
I think the only practical approach is an explicit "grow-only" setting
for auto-resize-tool-bars, and then define some specific commands
which may reduce the toolbar size (e.g. C-l as RMS suggested).
> Post-release, it would also be very nice to be able to specify the
> addition of a new row of toolbar buttons independent of frame width,
> for modes which append to the original set of buttons. This would
> also result in less churn in toolbar height, and would be more
> visually appealing for modes which add a themed set of icons.
I'm not sure I understand. Do you want a "line break" in the toolbar
lines or ?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-12-19 10:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 22:44 Toolbar redraw causes unwanted selection JD Smith
2006-12-14 17:47 ` Richard Stallman
2006-12-14 22:26 ` Kim F. Storm
2006-12-15 0:24 ` Kim F. Storm
2006-12-15 5:03 ` Richard Stallman
2006-12-15 10:09 ` Kim F. Storm
2006-12-15 10:33 ` David Kastrup
2006-12-15 13:33 ` Kim F. Storm
2006-12-15 21:24 ` Richard Stallman
2006-12-15 23:42 ` Kim F. Storm
2006-12-16 2:22 ` Werner LEMBERG
2006-12-16 9:53 ` Eli Zaretskii
2006-12-17 0:56 ` Kim F. Storm
2006-12-17 9:21 ` Jan Djärv
2006-12-17 5:36 ` Richard Stallman
2006-12-17 22:43 ` Kim F. Storm
2006-12-18 16:00 ` Richard Stallman
2006-12-19 10:07 ` Kim F. Storm
2006-12-19 22:54 ` David Kastrup
2006-12-20 13:01 ` Richard Stallman
2006-12-30 0:35 ` Kim F. Storm
2006-12-15 21:24 ` Richard Stallman
2006-12-15 22:22 ` David Kastrup
2006-12-18 16:14 ` JD Smith
2006-12-19 10:02 ` Kim F. Storm [this message]
2006-12-19 14:50 ` JD Smith
2006-12-19 16:09 ` Kim F. Storm
2006-12-29 5:52 ` JD Smith
2006-12-29 5:57 ` Nick Roberts
2006-12-29 6:07 ` JD Smith
2006-12-29 17:11 ` Kim F. Storm
2006-12-29 18:57 ` JD Smith
2006-12-29 23:38 ` Kim F. Storm
2006-12-30 18:23 ` Richard Stallman
2006-12-30 21:41 ` Kim F. Storm
2006-12-29 22:58 ` Richard Stallman
2006-12-29 23:41 ` Drew Adams
2006-12-30 18:23 ` Richard Stallman
2006-12-30 21:09 ` Drew Adams
2006-12-30 21:20 ` Drew Adams
2006-12-30 21:45 ` Kim F. Storm
2006-12-30 21:50 ` Drew Adams
2006-12-30 22:09 ` Kim F. Storm
2006-12-31 1:46 ` Richard Stallman
2006-12-20 13:00 ` Richard Stallman
2006-12-20 14:07 ` JD Smith
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=m3vek8b3uz.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@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).