all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith Russell <keithrussell42@fastmail.com>
Cc: 31203@debbugs.gnu.org
Subject: bug#31203: 26.1; Fringe and toolbar bitmaps unscaled on Windows 10 HiDPI display
Date: Wed, 18 Apr 2018 09:54:14 +0300	[thread overview]
Message-ID: <83vacp0zu1.fsf@gnu.org> (raw)
In-Reply-To: <cbb9ed83-fb25-40b8-94f5-9452a4d42a28@fastmail.com> (message from Keith Russell on Tue, 17 Apr 2018 21:07:34 -0400)

> From: Keith Russell <keithrussell42@fastmail.com>
> Date: Tue, 17 Apr 2018 21:07:34 -0400
> 
> 
> Running on Windows 10 with a high resolution display (3840 x 2160)
> the fringe bitmaps and toolbar buttons are so tiny as to be almost
> indistinguishable from dots. Scrollbars and menus are fine and the
> fonts look stunning. If I set the compatibility option to "override
> application" and let the system scale then it's the right size but
> fuzzy. I couldn't find anything in the bug reports. The only
> thing I found in the Changelog was the change to make Emacs
> DPI aware on Windows but that was back in 2015.

The fringe bitmaps have fixed width specified in pixels.  I understand
you are saying that the number of pixels is correct, but its visual
appearance leaves a lot to be desired, is that right?  If so, you can
customize your fringes using this:

  (setq fringe-mode '(16 . 16))

(replace 16 with a number that is to your liking, I'm just guessing
there).

We could also apply the scaling automatically, patches welcome.





  reply	other threads:[~2018-04-18  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18  1:07 bug#31203: 26.1; Fringe and toolbar bitmaps unscaled on Windows 10 HiDPI display Keith Russell
2018-04-18  6:54 ` Eli Zaretskii [this message]
2018-04-18 23:55   ` Keith Russell
2018-04-19  6:34     ` Eli Zaretskii
2019-09-11 15:55 ` bug#31203: Carlos Pita
2019-09-11 15:57   ` bug#31203: Carlos Pita
2019-09-11 16:24     ` bug#31203: Carlos Pita

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=83vacp0zu1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31203@debbugs.gnu.org \
    --cc=keithrussell42@fastmail.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 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.