From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <c9167f6cea8c715e0029b9f54cfe5a72@google.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio bug
From: "rob pike, esq." <r@geekmail.cc>
In-Reply-To: <5fd787a7923434da2f34205f4aa33bea@vitanuova.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 23 Mar 2004 11:45:43 -0800
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 3ef7338e-eacd-11e9-9e20-41e7f4b1d025

> that's a different problem as far as i'm aware - due to the fact that
> rio uses unbuffered windows to draw the borders.

not exactly. it's a consequence of the one major change in design between
8=C2=BD and rio.  8=C2=BD muxed all graphics ops, but rio only works as a=
 true
window manager.  under rio, programs write directly to the screen
through their own connection to /dev/draw.  the border bug is a
consequence of that coupled with my unwillingness to provide a 'grab'
operation to lock out drawing access.

-rob