Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!aplcen!haven!udel!new
From: new@udel.edu (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Double-Buffering in a window
Message-ID: <7501@nigel.udel.EDU>
Date: 5 Jan 90 16:09:14 GMT
References: <885@mindlink.UUCP> <1990Jan4.104416.15515@gdt.bath.ac.uk>
Sender: usenet@udel.EDU
Reply-To: new@udel.edu (Darren New)
Organization: University of Delaware
Lines: 19

In article <1990Jan4.104416.15515@gdt.bath.ac.uk> you write:
>In article <885@mindlink.UUCP> a464@mindlink.UUCP (Bruce Dawson) writes:
>>
>>     Screens are hardware entities, consisting of a set of rectangular (as
>>     Windows are software entities.  The illusion of hidden portions of windows
>Um, ok! But, a window still has an associated ViewPort,RastPort,BitMap etc. So
>you can still re-connect your own BitMap to the existing one,still have access
>to the copper lists through the ViewPort, and make use of RemakeDisplay() to
>re-calculate the copper lists. No?

I'm fairly sure that the ViewPort for all windows on the same screen is the
same pointer.  Also, I think the RastPort is a pointer into a bigger BitMap.
The only way to do what you want under intuition (as far as I know) is to
use a super-bitmap window (use your wheels, it is what they are for...)
This gives you a private area that can be scrolled onto and off of
another screen, but still probably not at full copper-pointing speed.
Consider that you cannot have two views on the same scanline...
How would you change a pointer on one window to have it display different
memory than the memory in the window just to the left of it? -- Darren