home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!mips!darwin.sura.net!tulane!agwbbs!dvtown!dvaz
- From: dvaz@dvtown.UUCP (David Vazquez)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: MakeScreen(); RethinkDisplay() vs. MakeVPort(); MrgCop(); LoadView()
- Distribution: world
- Message-ID: <dvaz.02wm@dvtown.UUCP>
- References: <1b5c1b9e.ARN5a25@moria.UUCP> <paulk.0ucw@terapin.com>
- Date: 22 Jul 92 14:19:07 CST
- Organization: Not an Organization
- Lines: 32
-
- In article <paulk.0ucw@terapin.com> paulk@terapin.com (Paul Kienitz) writes:
- >
- >That I had experienced. I have since heard of several people having
- >trouble, though.
- >
- >> ULONG iBaseLock = LockIBase(0);
- >>
- >> MakeVPort(&IntuitionBase->ViewLord, &screen->ViewPort);
- >> MrgCop(&IntuitionBase->ViewLord);
- >> LoadView(&IntuitionBase->ViewLord);
- >> UnlockIBase(iBaseLock);
- >>
- >
- >Now the question is, if this DOES really work, why the heck is
- >RethinkDisplay so damn slow?????
- >
-
- RethinkDisplay() is documented as going through every ViewPort in the Intui-
- tion display and analizing how to relates to the others--in particular the
- RKM: Includes and Autodocs mention that the VP_Hide bit is set accordingly
- for those ViewPorts that are not displayed. MrgCop() is called for ViewPorts
- that change then a LoadView() is performed. This is considerably alot more
- work than what the above five lines of code accomplish. The RKM: I&A also
- mentions that RethinkDisplay() may take several miliseconds and thus should
- not be used "ligthly".
-
- --
- ============================================================================
- // Look Ma, O David Vazquez \\
- // -|- INTERNET: dvaz%dvtown@cs.tulane.edu \\
- \X/ No hands. / \ USENET: ...!rex!dvtown!dvaz \X/
- ============================================================================
-