There is no point in loading our own link cursor, when AppKit supplies it through [NSCursor pointingHandCursor]
Created attachment 10858 [details] Patch to replace local TIFF cursor with NSCursor
Comment on attachment 10858 [details] Patch to replace local TIFF cursor with NSCursor Replaces the locally loaded TIFF pointing hand cursor with the system-supplied NSCursor
Comment on attachment 10858 [details] Patch to replace local TIFF cursor with NSCursor Our cursor has more demension than the built in cursor. We have a radar tracking this: <rdar://problem/4592353>
(In reply to comment #3) > (From update of attachment 10858 [details] [edit]) > Our cursor has more demension than the built in cursor. We have a radar > tracking this: <rdar://problem/4592353> > OK, I suppose we could remove the FIXME comment then :-)
Created attachment 12353 [details] adds dropshadow to link cursor (In reply to comment #3) > Our cursor has more demension than the built in cursor. I agree wholeheartedly. And why not set the standards ourselves? So here's a linkCursor with a slight drop shadow in it, like the arrow, alias and copy cursors. Maybe Apple will eventually backport it to Cocoa, so we can use it from there :-P
Comment on attachment 12353 [details] adds dropshadow to link cursor Without the white outline that the arrow cursor has, I think the drop shadow is a very subtle effect. Probably too subtle for anyone to notice. On the other hand, it does look slightly better, so r=me. When landing, please mention in the change log what's different about the cursor! And don't include the "WARNING: NO TEST CASES ADDED OR CHANGED". And please retitle this bug if it's going to be cited in the change log.
Committed revision 18878.