unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Bading <tbading@web.de>
To: emacs-devel@gnu.org
Subject: Re: The rabbit hole that is HiDPI... (empty menus / bug#31223 et al)
Date: Wed, 27 Nov 2019 13:29:32 +0100	[thread overview]
Message-ID: <7fa939cb-0af6-0450-6e9f-619f404b6a87@web.de> (raw)
In-Reply-To: <m236e9k14c.fsf@gmail.com>

On 27.11.19 12:30, Robert Pluim wrote:
 >     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.

Thanks, already found it. No comments on the color of my hair... ;-)

 > 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?

I'm trying to fix the mix.;-)
About to test whether two "req.height *= xg_get_scale (f);" in gtkutil.c
improve things.
(frame-monitor-workarea) is incorrect on my machine, too. Top is half of
what it should be.

 > BTW, which distribution and desktop environment is this? Ubuntu xx
 > with Gnome?

Ubuntu MATE Eoan.

 > PS. You might have more luck with emacs-27 and 'configure
 > --with-cairo'

Thanks for the hint. I'll give it a try when I have a patch that fixes
my current problems in 26.3.

Tobias




  reply	other threads:[~2019-11-27 12:29 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
2019-11-27 12:29   ` Tobias Bading [this message]
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=7fa939cb-0af6-0450-6e9f-619f404b6a87@web.de \
    --to=tbading@web.de \
    --cc=emacs-devel@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).