all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Felix E. Klee" <felix.klee@inka.de>, 20432@debbugs.gnu.org
Subject: bug#20432: GDK_SCALE=2 GDK_DPI_SCALE=0.5 destroys GTK+ 3 scroll bar
Date: Thu, 14 May 2015 19:57:18 +0200	[thread overview]
Message-ID: <5554E1FE.1090607@swipnet.se> (raw)
In-Reply-To: <5554CF7B.7090306@cs.ucla.edu>

Paul Eggert skrev den 2015-05-14 18:38:
> Thanks, Jan D., for looking into the problem.  It does appear to be a
> mess.  In theory I suppose Emacs should use
> gdk_screen_get_monitor_scale_factor to get the monitor scale factor; but
> in practice the situation is so messed up (and a lot of work would be
> needed to fix it) that it might not be worth bothering.
>
> By the way, on my Fedora 21 x86-64 host, setting GDK_SCALE=2
> GDK_DPI_SCALE=0.5 has no effect on emacs -Q, even with the recent
> fixes.  Perhaps this is due to the races you mentioned?

No, that just affects the initial frame size.
You should see an effect on toolbar and scroll bar size (they should be 
twice as big).  Are you compiling with Gtk+ 3.8 or later?

	Jan D.






  reply	other threads:[~2015-05-14 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 10:01 bug#20432: GDK_SCALE=2 GDK_DPI_SCALE=0.5 destroys GTK+ 3 scroll bar Felix E. Klee
2015-04-26 21:10 ` bug#20432: Further information (plus 1/2 workaround) Felix E. Klee
2015-05-14 11:34 ` bug#20432: GDK_SCALE=2 GDK_DPI_SCALE=0.5 destroys GTK+ 3 scroll bar Jan Djärv
2015-05-14 11:59   ` Felix E. Klee
2015-05-14 12:33     ` Jan Djärv
2015-05-14 12:46       ` Felix E. Klee
2015-05-14 13:13         ` Jan Djärv
2015-05-14 14:04           ` Felix E. Klee
2015-05-14 16:38 ` Paul Eggert
2015-05-14 17:57   ` Jan D. [this message]
2015-05-15  2:59     ` Paul Eggert
2015-05-15  7:01       ` Jan D.

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5554E1FE.1090607@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=20432@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=felix.klee@inka.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.