From: Carlos Pita <carlosjosepita@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37689@debbugs.gnu.org
Subject: bug#37689: Fringe pixmaps, widgets, etc. look ridiculously tiny in hidpi screen
Date: Thu, 10 Oct 2019 10:36:26 -0300 [thread overview]
Message-ID: <CAELgYhdtk8M=oySJo9LZCuCrVhy_4dTdP24WCsjz-gC0jBw8tQ@mail.gmail.com> (raw)
In-Reply-To: <83sgo1rpbx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Hi Eli,
> Please go ahead with making such an inventory, and thanks.
I've attached some cases. In general, this seems to be related to
hardcoded pixmaps. One option is to support at lease 1x, 1.5x and 2x
version, using the one that best accommodates to current resolution
(1.5x screens 1920x1080 are quite popular these days). Another options
is to patch the underlying renderer of these pixmaps so that it scales
them although I don't know if there is one single place to patch here.
> Please also verify that the situation hasn't changed in Emacs 27.
Yes, it's exactly the same.
[-- Attachment #2: Expand widget.png --]
[-- Type: image/png, Size: 7572 bytes --]
[-- Attachment #3: Flymake fringe indicator.png --]
[-- Type: image/png, Size: 926 bytes --]
[-- Attachment #4: Fringe wrap indicator.png --]
[-- Type: image/png, Size: 1612 bytes --]
[-- Attachment #5: Checkbox icons.png --]
[-- Type: image/png, Size: 87823 bytes --]
next prev parent reply other threads:[~2019-10-10 13:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 6:28 bug#37689: Fringe pixmaps, widgets, etc. look ridiculously tiny in hidpi screen Carlos Pita
2019-10-10 8:12 ` Eli Zaretskii
2019-10-10 13:26 ` Robert Pluim
2019-10-10 13:37 ` Carlos Pita
2019-10-10 13:47 ` Robert Pluim
2019-10-10 13:36 ` Carlos Pita [this message]
2019-10-10 14:21 ` Robert Pluim
2019-10-10 14:33 ` Carlos Pita
2019-10-10 14:37 ` Carlos Pita
2019-10-10 15:06 ` Eli Zaretskii
2019-10-10 15:43 ` Carlos Pita
2019-10-10 15:05 ` Eli Zaretskii
2019-10-10 15:51 ` Carlos Pita
2019-10-10 16:01 ` Carlos Pita
2019-10-10 17:35 ` Eli Zaretskii
2019-10-10 17:39 ` Carlos Pita
2019-10-11 3:26 ` Carlos Pita
2019-10-11 3:48 ` Carlos Pita
2019-10-12 0:51 ` Carlos Pita
2019-10-12 7:28 ` Eli Zaretskii
2019-10-12 7:56 ` Carlos Pita
2019-10-12 8:26 ` Carlos Pita
2019-10-14 0:40 ` Carlos Pita
2019-10-14 8:33 ` Eli Zaretskii
2019-10-14 13:19 ` Alan Third
2019-10-14 14:00 ` Eli Zaretskii
2019-10-17 11:48 ` Alan Third
2019-10-14 14:37 ` Carlos Pita
2019-10-14 14:54 ` Eli Zaretskii
2019-10-14 15:06 ` Carlos Pita
2019-10-14 15:15 ` Eli Zaretskii
2019-10-14 15:32 ` Carlos Pita
2019-10-14 16:52 ` Eli Zaretskii
2019-10-14 19:59 ` Carlos Pita
2019-10-14 23:42 ` Carlos Pita
2019-10-14 23:49 ` Carlos Pita
2019-10-15 1:50 ` Carlos Pita
2019-10-15 9:30 ` Eli Zaretskii
2019-10-15 23:01 ` Carlos Pita
2019-10-16 4:25 ` Carlos Pita
2019-10-16 9:16 ` martin rudalics
2019-10-16 16:31 ` Carlos Pita
2019-10-16 16:40 ` Carlos Pita
2019-10-16 19:01 ` Carlos Pita
2019-10-17 8:13 ` Robert Pluim
2019-10-15 9:27 ` Eli Zaretskii
2019-10-20 16:03 ` Juri Linkov
2019-10-20 17:37 ` Carlos Pita
2019-10-20 18:52 ` Juri Linkov
2019-10-20 19:17 ` Carlos Pita
2019-10-24 17:09 ` Carlos Pita
2019-10-26 10:45 ` Eli Zaretskii
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='CAELgYhdtk8M=oySJo9LZCuCrVhy_4dTdP24WCsjz-gC0jBw8tQ@mail.gmail.com' \
--to=carlosjosepita@gmail.com \
--cc=37689@debbugs.gnu.org \
--cc=eliz@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).