From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: hidpi
Date: Mon, 20 Dec 2021 14:34:38 -0500 [thread overview]
Message-ID: <9A97E4DBF184349630D38FE6DDD4A21B@eigenstate.org> (raw)
In-Reply-To: <a3c29669-44fb-4845-9db0-290b2f69f516@pixelhero.dev>
Quoth Noam Preil <noam@pixelhero.dev>:
>
> >> are you sure though that we need to do this on devdraw level?
> >
> > Not really sure to be honest, I only have a rough idea about libdraw or
> > how to exchange configuration options. At least in plan9port there is
> > also the new q(1d) command to query DPIs and 9fans.net/go/draw uses it
> > as well. I wonder whether this could be realized by just using
> > environment variables instead of configuring this through plan9.ini/the
> > result of q1d in drawterm.
>
> I think env variables are the wrong approach, at least in terms of ideal
> future behavior. With (hypothetical future) multimonitor support (or a
> short-term hack binding in a second machine's /dev/draw) you'd want
> per-monitor DPI configuration---i.e. if you start a program on one
> monitor, then move it to the other (with a /dev/draw shim which can be
> attached and detached from specific backends, and multiplexed, etc), DPI
> should change.
>
> I think devdraw is thus *exactly* where this information belongs, as DPI
> is dependent on the monitor, and that information is in devdraw's domain.
>
> - Noam Preil
>
Yes, but not in the draw device itself:
/dev/draw/geom
which presents a sequence of numbers, 6 to a line,
representing the screen rectangle in size and pixels;
each line represents one monitor.
libdraw and other programs that care can read this.
next prev parent reply other threads:[~2021-12-21 3:16 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 [this message]
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
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=9A97E4DBF184349630D38FE6DDD4A21B@eigenstate.org \
--to=ori@eigenstate.org \
--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).