home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!axion!spuddy!spark
- From: spark@spuddy.uucp (Steve)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: MakeScreen(); RethinkDisplay() vs. MakeVPort(); MrgCop(); LoadView()
- Message-ID: <1992Jul22.192458.5966@spuddy.uucp>
- Date: 22 Jul 92 19:24:58 GMT
- References: <1b5c1b9e.ARN5a25@moria.UUCP> <paulk.0ucw@terapin.com>
- Organization: Spuddy's Public Usenet Domain
- Lines: 29
-
-
- It's about time the slowness of ReThinkDisplay() was discussed. If
- it wasn't so slow, we'd e able to hvae copper scrolling, among other things.
-
- For those not au fait, with copper scrolling, it invloves setting up a
- copper list with two accesses to the bitplane data in it.
-
- One access is at the top of the viewport, and the other access is x pixels
- down.
-
- To scroll the viewport, you simply change the first access, to make the
- bitplane pointers point (say) 8 pixels further down the screen. Then
- you make x -= 8. Position x is where you reload the bitplane pointers
- with the start of the display data.
-
- Well - anyway - the point is that you'd be able to scroll a whole screen
- really smoothly, using virtually no processor time, no blitter,
- many times faster than the blitter, with no flicker, if it wasn't for the
- slowness of ReThinkDisplay()
-
- If CBM can't speed up RTD(), how about adding some kind of special support
- for the above kind of scrolling. Sure would make text editors look nice.
-
- Steve
-
- --
-
- ---- Steve Parkinson (spark%spuddy.uucp@uknet.ac.uk) ----
- ----- Call Spuddy for Free UK USENET on 0203 638780 -----
-