home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!yale!gumby!destroyer!ubc-cs!uw-beaver!news.u.washington.edu!glia!bjackson
- From: bjackson@glia.biostr.washington.edu (Ben Jackson)
- Subject: Re: MakeScreen(); RethinkDisplay() vs. MakeVPort(); MrgCop(); LoadView()
- Message-ID: <1992Jul25.155709.15168@u.washington.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: Dept Biological Structure-University of Washington
- References: <paulk.0ucw@terapin.com> <1992Jul22.192458.5966@spuddy.uucp> <33307@cbmvax.commodore.com>
- Date: Sat, 25 Jul 1992 15:57:09 GMT
- Lines: 25
-
- In article <33307@cbmvax.commodore.com> peter@cbmvax.commodore.com (Peter Cherna) writes:
- >RethinkDisplay() is the general "I munged a screen, please make everything
- >happy again" function. We're not going to supply specialized mini-versions
- >to handle each potential sub-case.
-
- I was reading along happily and nodding to myself until I came to this
- paragraph... While I can agree that it is reasonable to require that
- RethinkDisplay() be called on Intuition screens, I think you're going
- too far with that description. In order to use sprites or BOBs, you have
- to call RethinkDisplay() after you've moved and resorted your objects.
- That's a major hit. It's not something I'm calling frivolously, it's
- something I *have* to call, and in a fairly tight loop. (or what would be
- a tight loop without RD()).
-
- It's depressing to replace MakeScreen/RethinkDisplay with MakeVPort/
- MrgCop/LoadView and watch the program speed up by an order of magnitude.
- It's bad enough that the VSprites are flickering like crazy. :-\
-
-
- > Peter
- >--
- >Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
-
-
-
-