Path: utzoo!mnetor!uunet!iscuva!jimc
From: jimc@iscuva.ISCS.COM (Jim Cathey)
Newsgroups: comp.sys.mac
Subject: Re: Control Panel Bug?
Message-ID: <1022@iscuva.ISCS.COM>
Date: 4 Jan 88 21:09:06 GMT
References: <9931@ut-sally.UUCP> <3646@husc6.harvard.edu> <9948@ut-sally.UUCP> <3670@husc6.harvard.edu>
Organization: ISC Systems Corporation, Spokane, WA
Lines: 23

In article <3670@husc6.harvard.edu> singer@endor.UUCP (Rich Siegel) writes:
>In article <9948@ut-sally.UUCP> brian@ut-sally.UUCP (Brian H. Powell) writes:
>>guess the question is, "Does SetCursor make a copy of the cursor & use that,
>>or does it use the actual cursor that it's given?"  If it's the latter, I'll

>	Strictly speaking, this could (and probably will) break in the future,
>sometime, but for now it's probably safe. If I had to guess I'd say that 
>SetCursor will copy the cursor and use CopyBits to stamp its image on
>the screen.

I can't speak for Color Quickdraw, but the older Mac ROMs copy the SetCursor
data into low-memory globals where the low-level mouse handlers can use it.
Copybits isn't used at all, the mouse driver itself is nearly autonomous (and
was probably written and running before Quickdraw was).

+----------------+
! II      CCCCCC !  Jim Cathey
! II  SSSSCC     !  ISC Systems Corp.
! II      CC     !  Spokane, WA
! IISSSS  CC     !  UUCP: ihnp4!tektronix!reed!iscuva!jimc
! II      CCCCCC !  (509)927-5757
+----------------+
			"With excitement like this, who is needing enemas?"