Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!imagen!atari!kbad
From: kbad@atari.UUCP (Ken Badertscher)
Newsgroups: comp.sys.atari.st
Subject: Re: how to kill a mouse cursor
Message-ID: <1451@atari.UUCP>
Date: 13 Apr 89 19:44:13 GMT
References: <8904051001.AA18434@ucbvax.Berkeley.EDU>
Reply-To: kbad@atari.UUCP (Ken Badertscher)
Organization: Atari Corp., Sunnyvale, CA
Lines: 24

In article <8904051001.AA18434@ucbvax.Berkeley.EDU> USQB015@LIVERPOOL.AC.UK writes:
|Easy,
|     Use A-line instruction 10 $a i.e. opcode $a00a

That's also a good way to get the AES confused about how many times the
mouse has been hidden/shown.  The AES keeps its own internal count of
how many times the mouse has been hidden or shown so that it can clean
up after applications that go astray with the mouse.  This AES count
will get out of sync with the actual mouse state if you interleave
VDI/line-A show/hide mouse calls with AES graf_mouse calls.
 
  So the answer to the question how to kill a mouse cursor isn't all
that easy.  If your program uses the AES a lot, you should probably use
the AES graf_mouse() calls to hide and show the mouse.  If not, use VDI
or even line-A.  You could even disable mouse event reporting at the
IKBD level if you wanted to go so far.

|             Mark Powell


-- 
 Ken Badertscher                 | #include <disclaimer>
 Atari R&D                       | No pith, just a path:
 Software Engine                 |   {portal,ames,imagen}!atari!kbad