From: Richard Hansen <rhansen@rhansen.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
56607@debbugs.gnu.org
Subject: bug#56607: 29.0.50; (setq auto-resize-tool-bars 'grow-only) has no effect (pgtk)
Date: Sun, 17 Jul 2022 23:37:20 -0400 [thread overview]
Message-ID: <f36a408e-1490-5715-3eee-15ffb9d0b0a3@rhansen.org> (raw)
In-Reply-To: <87a697dyu3.fsf@yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]
Po Lu wrote:
> Richard Hansen <rhansen@rhansen.org> writes:
>
>> Can the toolbar be nested inside a container widget whose size we can
>> control?
>
> Perhaps, but then we would only be controlling the size of that widget,
> and not the toolbar itself.
Can the dimensions of the toolbar be inspected? If so, we can force the container widget to never shrink if `auto-resize-tool-bars' is `grow-only'.
>
> GTK toolbars don't wrap extra items, they truncate them. So
> `auto-resize-tool-bars' has no real chance of working anyway.
If the toolbar width changes, we could do the (un)wrapping ourselves: move the buttons to/from another toolbar underneath the upper toolbar. The lower toolbar would still be inside the same container widget as the upper toolbar, and `grow-only' would pay attention to the sum of the heights of the toolbars. Would that work?
(Sorry for all of the questions; I'm not familiar with GTK. But I'm willing to spend some time to cook up some patches if given some hints on how to tackle the problem.)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-18 3:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 1:52 bug#56607: 29.0.50; (setq auto-resize-tool-bars 'grow-only) has no effect (pgtk) Richard Hansen
2022-07-17 5:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 5:57 ` Eli Zaretskii
2022-07-17 10:02 ` Eli Zaretskii
2022-07-17 23:37 ` Richard Hansen
2022-07-18 0:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 3:37 ` Richard Hansen [this message]
2022-07-18 4:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 5:43 ` Richard Hansen
2022-07-18 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 9:20 ` Lars Ingebrigtsen
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=f36a408e-1490-5715-3eee-15ffb9d0b0a3@rhansen.org \
--to=rhansen@rhansen.org \
--cc=56607@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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).