unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: What is the proper way to scale fringe-bitmaps for high-DPI displays?
Date: Wed, 20 Mar 2019 17:17:16 -0400	[thread overview]
Message-ID: <cfd19b91-aac9-cb7e-e958-af4fa48a2ef3@gmail.com> (raw)
In-Reply-To: <83ftrhs3lu.fsf@gnu.org>

On 2019-03-20 16:17, Eli Zaretskii wrote:
>> Cc: emacs-devel@gnu.org
>> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
>> Date: Wed, 20 Mar 2019 16:05:48 -0400
>>
>>> The frame's parameters is a better way if we think such a parameter
>>> will be useful to Lisp programs, and calling a function for that is
>>> too much overhead.  Otherwise, a simple field of 'struct frame' will
>>> be somewhat less hassle, because you don't need to mess with the likes
>>> of frame-parameter to teach them about this new parameter.  But either
>>> way, the job is not hard.
>>
>> Oh, so Emacs' C code would scale the bitmaps? I expected the Lisp code would do that.
> 
> Fringes are displayed in C.  Doing this in Lisp will produce
> flickering, I'm afraid.

I thought the C code would read the scaling factor and set the bitmap accordingly just once, when creating overlays or applying text properties.



  reply	other threads:[~2019-03-20 21:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 14:55 What is the proper way to scale fringe-bitmaps for high-DPI displays? Clément Pit-Claudel
2019-03-20 17:32 ` Eli Zaretskii
2019-03-20 19:34   ` Clément Pit-Claudel
2019-03-20 19:44     ` Eli Zaretskii
2019-03-20 20:05       ` Clément Pit-Claudel
2019-03-20 20:17         ` Eli Zaretskii
2019-03-20 21:17           ` Clément Pit-Claudel [this message]
2019-03-21  3:32             ` Eli Zaretskii
2019-03-21 11:43               ` Daniel Pittman
2019-03-21 13:33                 ` Yuri Khan
2019-03-21 14:32                   ` Eli Zaretskii
2019-03-21 17:32                     ` Alex
2019-03-21 18:31                       ` Eli Zaretskii
2019-03-21 17:38                     ` Clément Pit-Claudel
2019-03-21 18:33                       ` Eli Zaretskii
2019-03-21 17:40               ` Clément Pit-Claudel
2019-03-20 19:37   ` Clément Pit-Claudel
2019-03-21 15:24   ` Dmitry Gutov
2019-03-21 16:02     ` 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=cfd19b91-aac9-cb7e-e958-af4fa48a2ef3@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --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).