From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: hidpi
Date: Tue, 21 Dec 2021 09:37:07 +0100 [thread overview]
Message-ID: <CAFSF3XOD+6UmQjQAAP2zSFYbSNkKpbk89iYqT=cbsMwDSJ7nUw@mail.gmail.com> (raw)
In-Reply-To: <wo4DyzXmHiFPY4InC7mnvBHoCjRtpkrmlOhr_aQ3bNZfXZAVmU4fIXkGYPX3kxgpjjO-nuitcytmmn5-Mgx8BeeJKfPgyZiEDVYRnkovCog=@protonmail.com>
yes, a more neutral scaling factor sounds like it would confuse less people.
and locking in with the fontsizes sounds like a great idea to me!
On 12/21/21, Philip Silva <philip.silva@protonmail.com> wrote:
> On the other hand speaking of different viewing distances/ideal widget sizes
> when things should be larger or smaller, it might be necessary to lie about
> mm (or dpi). Another option would be to just define scaling factors so
> scrollbars have practical sizes:
>
> 0 0 3840 2160 2.2 2.2
>
> (Also I wonder if making widget sizes like scrollbar widths a pre-defined
> multiple of the font height would already work... Or if it's necessary to
> scale both independently)
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Monday, December 20th, 2021 at 21:50, <ori@eigenstate.org> wrote:
>
>> Quoth ori@eigenstate.org:
>>
>> > the screen rectangle in size and pixels;
>>
>> er. in pixels and mm, eg:
>>
>> # x0 y0 x1 y1 width height
>>
>> 0 0 3840 2160 527 296
>
next prev parent reply other threads:[~2021-12-21 8:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:13 [9front] hidpi Philip Silva
2021-12-20 16:34 ` hiro
2021-12-20 17:04 ` [9front] hidpi Philip Silva
2021-12-20 17:29 ` hiro
2021-12-20 19:15 ` Noam Preil
2021-12-20 19:34 ` ori
2021-12-20 20:50 ` ori
2021-12-20 21:10 ` hiro
2021-12-20 21:19 ` ori
2021-12-20 22:02 ` sirjofri
2021-12-21 0:29 ` Philip Silva
2021-12-21 8:37 ` hiro [this message]
2021-12-20 21:47 ` Noam Preil
2021-12-20 17:59 ` [9front] hidpi igor
2021-12-20 18:28 ` hiro
2021-12-20 19:27 ` Noam Preil
2021-12-20 19:02 ` Philip Silva
2021-12-22 8:39 ` igor
2021-12-22 11:31 ` Philip Silva
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='CAFSF3XOD+6UmQjQAAP2zSFYbSNkKpbk89iYqT=cbsMwDSJ7nUw@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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.
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 NNTP newsgroup(s).