Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!bcm!dimacs.rutgers.edu!rutgers!cbmvax!cbmehq!cbmdeo!icoast!hbrinch From: hbrinch@icoast.UUCP (Henrik Brinch) Newsgroups: comp.sys.amiga.programmer Subject: Re: Lemmings - a tutorial Part V (last) Message-ID: <18eada2a.ARN0f36@icoast.UUCP> Date: 1 Apr 91 10:27:38 GMT References: <23788@well.sf.ca.us> <23837@well.sf.ca.us> <781@tnc.UUCP> <20213@cbmvax.commodore.com> Reply-To: hbrinch@icoast.UUCP Followup-To: comp.sys.amiga.programmer Organization: InfoCoast Technologies Lines: 30 In article <20213@cbmvax.commodore.com>, Randell Jesup writes: > >How long does MrgCop() take (pick random number). How long does > >RethinkDisplay() take (seconds)? How long does BltMaskBitMapRastPort() > >take? > > (1) those are not called all the time, (2) you're exaggerating > by a lot. BMBMRP() is not fast because it operates on arbitrary rectangles, > and some sets require using the A-channel as a mask. So if you do know > the alignments are ok, OwnBlitter() and program it directly. > About #2 he's _NOT_ exaggerating the RethinkDisplay() is WAY TOO SLOW(!) I've written a little utility on my A3000 (25Mzh) and it worked perfectly, then trying it on a standard A2000 I got a shock. My task was to change some colors in the copperlist (on an intuitionscreen), I've tried but the only way to do this is to remake the whole copperlist and refreshing the display (which is too slow). Indeed a lot of OS routines are fast (and would be stupid vasting time writing yourself) but others are simply too slow to be used (even in utilities :(!) > Randell Jesup, Keeper of AmigaDos, Commodore Engineering. > {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Best Regards, InfoCoast /\ /\_ Henrik Brinch \ cbmehq!cbmdeo!icoast!hbrinch Technologies /\/ \/ \ Kloevervej 7 \ FidoNet 2:230/112.3 ____________/ \ / \ 2800 Lyngby \ Voice/Fax tel.# +45 42 87 67 23 / \/ \ Denmark \ "C is SILVER - But ASM is GOLD"