On Apr 23, 2008, at 6:44 PM, Quincey Morris wrote:
On Apr 23, 2008, at 08:10, an0 wrote:
Chances are, calling '[[self enclosingScrollView]
setDocumentCursor:[NSCursor closedHandCursor]]' in 'mouseDown:'
will fix the
problem you're seeing. NSScrollView/NSClipView's way of changing
the cursor
conflicts with autoscrolling or drag-scrolling, but AFAIK there's
no way of
preventing that interference directly.
This partially works. However, if you move the item off the visible
part of scroll view and then move back, you'll find a arrowCursor
instead of openHandCursor when cursor hovers on the item. It seems
cursor problems pervade Cocoa applications and Apple just ignores
them:(
Does this sample application still use cursorRects/NSTrackingRects?
Leopard introduced a new mechanism -- NSTrackingArea and
cursorUpdate events -- which doesn't have some of the problems that
the old mechanism supposedly had.
Yes it does. It should be updated to use the new API, but hasn't been
as yet.
File enhancement bugs as you feel appropriate.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
