On 3/1/05 4:40 AM, Mike Kluev didst favor us with:
>>> I think the poster's intention was that InitCursor would set the
>>> cursor back, and show it. I don't know whether this is actually the
>>> case. If not, another SetThemeCursor call followed by ShowCursor
>>> should work. In fact, I would think calling InitCursor anytime after
>>> having made cursor calls would be an iffy way to do things; is that
>>> really its intended usage?
>>
>> Except that InitCursor doesn't "set it back." It sets it to the arrow
>> cursor. If the cursor was the hand cursor when this process started, for
>> example, it would change from the hand to an arrow when this happens, and
>> that's more noticeable than a 1-tick flicker.
>
> ok...
>
> 1) QDGetCursorData (to save the current cursor)
I believe the OP has a Cocoa application that isn't using a QD cursor whose
data he can save at this point. At least that's how I understood it.
Larry
> 2) HideCursor
> 3) SetThemeCursor
> 4) QDGetCursorData again
> 5) Now restore cursor to (1)
> 6) ShowCursor
> 7) Now convert cursor image from (4) to NSCursor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
