Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!princeton!udel!rochester!cornell!uw-beaver!mit-eddie!husc6!linus!necntc!ames!sri-spam!mordor!lll-lcc!well!ewhac
From: ewhac@well.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Sprites
Message-ID: <4094@well.UUCP>
Date: Wed, 30-Sep-87 16:57:05 EDT
Article-I.D.: well.4094
Posted: Wed Sep 30 16:57:05 1987
Date-Received: Sat, 3-Oct-87 02:25:20 EDT
References: <1758@crash.CTS.COM> <1659@gryphon.CTS.COM> <4034@well.UUCP> <1686@gryphon.CTS.COM>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: Lazy Programmers, Ltd.
Lines: 28

In article <1686@gryphon.CTS.COM> jdow@gryphon.CTS.COM (Joanne Dow) writes:
>In article <4034@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>>In article <1659@gryphon.CTS.COM> jdow@gryphon.CTS.COM (Joanne Dow) writes:
>>>Overscan eats into sprite time.  If you overscan enough you can even 
>>>eat into the mouse sprite's time and even IT becomes a verticle bar. [...]
>>
>>	More egg, Joanne....			:-) :-)
>>
>>	There is a hardware stop for display DMA at data fetch cycle $18.
>
>Your turn for something akin to egg. There may be such a stop; but, I have a
>program that stomps the mouse cursor. The latest Showanim (4.0) is the guilty
>party. [ ... ]

	Sigh.  My information came from the mystic DMA timing chart that
everyone says isn't in the A/W Hardware manual but really is.  There's a
notation saying that a hardware stop is at cycle $18.

	Well that's what it said.....

	Regarding your screwed up mouse cursor: what do you want to bet that
they are SetPointer()ing to a blank sprite image that isn't in CHIP RAM?

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	ihnp4!ptsfa -\
 \_ -_		Recumbent Bikes:	      dual ---> !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor