🚀 go-pugleaf

     In a program I'm working on, I load all the cursors that I am going to
use at the beginning of the program, move them to high memory, lock them down,
dereference the handles and use pointers to them for the duration of the
program.  Fine.
     After playing around with the control panel, I noticed that my watch
cursor had turned into mush.  I tried a few other DAs, but I couldn't get them
to exhibit this behavior.  I did a step spy on the handle and found out that
somebody is unlocking the handle.  I'm not sure if it's the control panel or
the OpenDeskAcc code, but it happens in there somewhere.
     This all reeks of good old Macintosh Technical Note #1, in which is
discussed the issue of DAs purging system resources, for example, oh, say the
watch cursor, that might be in use by the application.  This makes me tend to
believe that the DA is wrong in unlocking my handle.  (As opposed to me being
wrong expecting locked handles to system resources to stay locked.)

     Any comments?  I plan to refetch my cursors after the OpenDeskAcc call
now, rather than call GetCursor each time I want to use a cursor.  Is this
safe?  Are there any other things lurking about that want to unlock my
handles?

Brian H. Powell
		UUCP:	...!uunet!ut-sally!brian
		ARPA:	brian@sally.UTEXAS.EDU

		P.O. Box 5899
		Austin, TX 78763-5899
		(512) 346-0835