Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pa.dec.com!bacchus!mwm From: mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga.programmer Subject: Re: Mouse blanking Message-ID: Date: 7 May 91 16:37:24 GMT References: <9107@crash.cts.com> Sender: news@pa.dec.com (News) Organization: Missionaria Phonibalonica Lines: 30 In-Reply-To: hawk@pnet01.cts.com's message of 7 May 91 04:16:03 GMT In article <9107@crash.cts.com> hawk@pnet01.cts.com (John Anderson) writes: >not thinking of it, of simply turning off sprite DMA to blank the >mouse. Entirely compatible and documented. Works great! And if it >ever breaks in the future you simply turn off that particular feature. Turning off sprite DMA to blank the mouse pointer may be good for some things but the people who wrote the few pointer blankers for 2.0 also turned off the cursor for JRComm (which is a sprite). So when the mouse pinter blanks so does the darn cursor!!! As one of those authors, I can tell you it's not avoidable. Turning off sprite DMA (the safe way to turn it off) turns off all the sprites. That's the way the hardware works. Since MouseOff is a commodity, use Exchange to disable it when you're running JRComm (or anything else that needs sprites). Now, if you want to suggest another way to turn off the cursor that's 2.0 safe (doesn't even need to work in 1.3), I'll gladly consider it. Matt, what does DMouse do to prevent the sprite dma from being turned off while a sprite is being displayed? I'm still trying to find a good solution to that.