From: Robert Pluim <rpluim@gmail.com>
To: Tobias Bading <tbading@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: The rabbit hole that is HiDPI... (empty menus / bug#31223 et al)
Date: Wed, 27 Nov 2019 12:30:27 +0100 [thread overview]
Message-ID: <m236e9k14c.fsf@gmail.com> (raw)
In-Reply-To: <ac283b88-4ff1-8daf-a8f8-e02de1bf161d@web.de> (Tobias Bading's message of "Tue, 26 Nov 2019 20:13:21 +0100")
>>>>> On Tue, 26 Nov 2019 20:13:21 +0100, Tobias Bading <tbading@web.de> said:
Tobias> But seriously... what would be the proper way to deal with HiDPI in
Tobias> Emacs? Has anyone done any work on this?
xg_get_scale(). And yes, which is why my hair is turning grey.
Tobias> I don't have much experience with GTK or HiDPI solutions on GNU/Linux in
Tobias> general. From what I've debugged so far it seems that GTK works similar
Tobias> to CSS, with some form of abstract pixels, which are mapped to 2x2
Tobias> device pixels in my case. Since the low-level X11 APIs and events still
Tobias> seem to use actual device pixels, would it make sense to look for the
Tobias> source of the halved values returned by FRAME_MENUBAR_HEIGHT(f) et al
Tobias> and multiply these by two in my case?
Yes, if you have scaling in GTK the number of pixels as seen by GTK is
scaled up or down. Unfortunately too much code in Emacs still works in
device pixels. Who will rid us of this turbulent mix of X and GTK?
BTW, which distribution and desktop environment is this? Ubuntu xx
with Gnome?
Robert
PS. You might have more luck with emacs-27 and 'configure
--with-cairo'
next prev parent reply other threads:[~2019-11-27 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 19:13 The rabbit hole that is HiDPI... (empty menus / bug#31223 et al) Tobias Bading
2019-11-26 19:24 ` Tobias Bading
2019-11-27 11:06 ` Tobias Bading
2019-11-27 11:30 ` Robert Pluim [this message]
2019-11-27 12:29 ` Tobias Bading
2019-11-27 13:00 ` Robert Pluim
2019-11-27 13:41 ` Tobias Bading
2019-11-27 15:12 ` Robert Pluim
2019-11-27 16:41 ` Tobias Bading
2019-11-27 17:00 ` Robert Pluim
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=m236e9k14c.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=tbading@web.de \
/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).