unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Richard Hansen <rhansen@rhansen.org>
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: Mon, 18 Jul 2022 14:24:15 +0800	[thread overview]
Message-ID: <87o7xnc50w.fsf@yahoo.com> (raw)
In-Reply-To: <dfad0cec-4121-ae54-0fc6-727bca03d942@rhansen.org> (Richard Hansen's message of "Mon, 18 Jul 2022 01:43:32 -0400")

Richard Hansen <rhansen@rhansen.org> writes:

> What I mean is we would inspect the size of the toolbar (before any
> clipping required to fit inside the container widget) then adjust the
> size of the container widget appropriately.

I'm not sure what you're talking about.  What is being clipped to fit
inside the container widget?

> That's a good point.  Out of curiosity I looked into GTK4 and they did
> away with the toolbar class.  Users should instead use a GtkBox
> containing buttons, and apply appropriate styling.  libadwaita
> provides a toolbar style class for this purpose [1].  I'm guessing it
> would be straightforward to implement toolbar button wrapping in GTK4,
> if/when Emacs migrates to it.

It will be more straightforward to implement tool-bar wrapping.

But I gave up on the GTK 4 work I was doing, since GTK 4 is simply not
ready: it doesn't even support subpixel anti-aliasing, and has many
regressions compared to GTK 3 when it comes to display synchronization,
drag-and-drop, and selections.





  reply	other threads:[~2022-07-18  6:24 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
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 [this message]
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=87o7xnc50w.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56607@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=rhansen@rhansen.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).