From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <31ec63c8fe239f38e1b5b53cf8215c8b@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 27 Feb 2009 17:48:40 -0500
To: 9fans@9fans.net
In-Reply-To: <6106b83c758fd550764970aba53bd530@mail.nanosouffle.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] rio Peculiarities
Topicbox-Message-UUID: a9fe8b26-ead4-11e9-9d60-3106f5b1d025

On Fri Feb 27 16:46:34 EST 2009, akumar@mail.nanosouffle.net wrote:
> Having a window which is `current' and `visible' but not on `top'
> gives rise to some effects of concern.  For example, scrolling this
> current window is cause for massive load on the system; if there are
> windows on top, making them current requires hiding the current one
> (clicking on them is ineffective).  My use for being in such a
> situation is, e.g., scrolling some acme body in the background while
> doing something with an rc window on the foreground (since my acme
> window takes up a large part of the screen).

take a look at the pat patch or the older mtrr patch.

- erik