From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio bug
Date: Tue, 23 Mar 2004 19:30:40 +0000 [thread overview]
Message-ID: <5fd787a7923434da2f34205f4aa33bea@vitanuova.com> (raw)
In-Reply-To: <67c9a432fcc5efbb15356107e3a5b658@plan9.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
> it is a more serious problem that requires changes deep in Plan 9's
> drawing library and we see it all the time without it even bothering
> us -- try dragging a window border over something that does draw() in
> the meantime and you'll get a leftover red streak from the border.
> the solution is to slightly resize the original window causing a new
> draw() to refresh it.
that's a different problem as far as i'm aware - due to the fact that
rio uses unbuffered windows to draw the borders.
[-- Attachment #2: Type: message/rfc822, Size: 2383 bytes --]
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio bug
Date: Tue, 23 Mar 2004 12:19:30 -0700
Message-ID: <67c9a432fcc5efbb15356107e3a5b658@plan9.ucalgary.ca>
> that sounds like a workaround rather than a solution.
> the solution is to make the behavior go away completely.
>
> russ
it is a more serious problem that requires changes deep in Plan 9's
drawing library and we see it all the time without it even bothering
us -- try dragging a window border over something that does draw() in
the meantime and you'll get a leftover red streak from the border.
the solution is to slightly resize the original window causing a new
draw() to refresh it.
yes, it's a workaround. nobody seems bothered by it enough to solve
the problem though (well, in my case i don't know how, so i'm excused)
oops, looks like my "workaround" won't work anyway, so it's only an
"around" -- back to where we started :)
andrey
next prev parent reply other threads:[~2004-03-23 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 18:53 andrey mirtchovski
2004-03-23 19:04 ` Russ Cox
2004-03-23 19:15 ` rog
2004-03-23 19:19 ` andrey mirtchovski
2004-03-23 19:30 ` rog [this message]
2004-03-23 19:45 ` rob pike, esq.
2004-03-23 23:49 ` Geoff Collyer
2004-03-24 4:35 ` rob pike, esq.
2004-03-24 7:54 ` Fco.J.Ballesteros
2004-03-23 19:50 ` rog
2004-03-23 19:51 ` rob pike, esq.
2004-03-23 19:47 ` rob pike, esq.
2004-03-23 20:09 ` boyd, rounin
2004-03-23 19:30 matt
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=5fd787a7923434da2f34205f4aa33bea@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).