From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4f825ab42d917c07bf62fd6cb259bb55@vitanuova.com>
To: 9fans@cse.psu.edu
From: rog@vitanuova.com
In-Reply-To: <Pine.LNX.4.44.0403042140450.7453-100000@maxroach.lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] borders
Date: Fri,  5 Mar 2004 18:45:07 +0000
Topicbox-Message-UUID: 19e0bdb8-eacd-11e9-9e20-41e7f4b1d025

> Which led to some curiousity for me: any reason that there is a border in 
> (I guess) libdraw?

getwindow() knows about rio borders (it gets the named image which is
the rio window, then creates the application's window inside a screen
inside that).

this area is a little fragile (there's a race which means that
getwindow() can return nil even though there is a window to be got;
it's quite easy to crash acme this way, for example).