From: Philip Silva <philip.silva@protonmail.com>
To: 9front@9front.org
Subject: Re: [9front] hidpi
Date: Wed, 22 Dec 2021 11:31:42 +0000 [thread overview]
Message-ID: <lJHQNl7ydPwQGDrwQr8mrTrZviqfQu91rBHEkKWcBMKwUYtIB9Z_aGDotJ4wAo8rwlOn4PK0ngnVO4ifUy0VlEqn1sd_1MX6qEgAB9uCdBU=@protonmail.com> (raw)
In-Reply-To: <EB4EE1A4B8CF518C2ADC0A9B72E40509@9lab.org>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
Ah ok, interesting. The one I remember is actually a similar y offset problem but in the opposite side (drawing into the now thicker border on top). That was in rio though. I must admit I mechanically copied the changes from plan9port where it seemed reasonable and then continued replacing where it looked right. So that code has kind of heuristic reasoning :) Cool I'll probably look first into trying some of the ideas mentioned once I'm in reach of my laptop again
-------- Original Message --------
On Dec 22, 2021, 9:39 AM, < igor@9lab.org> wrote:
Quoth Philip Silva <philip.silva@protonmail.com>:
[…]
> - glitches: the borders aren't calculated correctly (3rd patch for rio and acme is very wip)
[…]
By glitches, do you mean issues like the one here:
• https://9lab.org/img/plan9/acid.png
…where there is an issue in computing the column growth ⁽¹⁾ (I think)
manifesting itself as an artefact that looks like a white line at the
bottom of an acme column. On small res displays this isn't
noticeable, however, on high-res screens it is annoying.
I stopped half way through due to lack of time debugging this
(still on my todo list), and was wondering if you observed the
same glitch.
⁽¹⁾ … https://9lab.org/plan9/debugging-with-acid/
[-- Attachment #2: Type: text/html, Size: 1438 bytes --]
next prev parent reply other threads:[~2021-12-23 0:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:13 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
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 [this message]
2021-12-23 13:11 igor
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='lJHQNl7ydPwQGDrwQr8mrTrZviqfQu91rBHEkKWcBMKwUYtIB9Z_aGDotJ4wAo8rwlOn4PK0ngnVO4ifUy0VlEqn1sd_1MX6qEgAB9uCdBU=@protonmail.com' \
--to=philip.silva@protonmail.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).