Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ll-xn!mit-eddie!genrad!decvax!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Re: layers and cliprects
Message-ID: <8707021246.AA00762@cogsci.berkeley.edu>
Date: Thu, 2-Jul-87 08:46:36 EDT
Article-I.D.: cogsci.8707021246.AA00762
Posted: Thu Jul  2 08:46:36 1987
Date-Received: Sat, 4-Jul-87 05:25:57 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27

In article <> dale@amiga.UUCP (Dale Luck) typed:
<In article <> bryce@cogsci.berkeley.EDU (Bryce Nesbitt) typed:
<< To toss an obvious idea out... how about a priority -200 task that coagulates
<< optimizes cliprects and frees the extra chip memory taken up by the above
<< situation?
<
< The Cliprects are coagulated after every internal delete layer operation.
< MoveLayer and SizeLayer both use internal delete.  [...]  The only thing
< that prevents completion of the dedicer is memory constraints. poof.
> [If it can't find enough if gives up till next time...]

I checked and that's right (of course it's right, he wrote the thing, silly).

Other layer weirdness: Take a machine with only a CLI and do a <esc>[43m.
(Background becomes red).  Load sys:utilities/clock.  Center the clock
on the screen and push it behind the CLI.  Press CTRL-L.  Now resize the
CLI just a bit.  The area of the obscured clock window will "show
through" for a moment.  This behavior was what caused the asumption that
there where dirty cliprects and/or fragmented bitmaps.  (That and
my defective expansion ram :-)


Is there any hope for a future one step size and move layer?  And (talking
through my hat now) Poof() and UnPoof() which would move a layer totally
off-screen yet still allow normal rendering to occur?  (Also create the
layer off-screen, prepare it, then present it to the world).  (Besides
the hack of hiding it behind a backdrop layer...)