On Feb 4, 2009, at 19:28, Luke Evans wrote:
Mmm. I'm going to have to check with you what this "fudgy thing" actually is, in case I'm not doing something that is required (officially or conventionally) to make things work. Certainly, I was doing all my autoscroll during receipt of NSPeriodic events, at which point the view was requested to scroll and I attempted to refresh my tracking areas as mentioned - nothing more. I was expecting subsequent events to arrive with correct mouse positions relative to the view when transformed per usual from window to view coords. Is there some extra offset from the beginning of the drag, or some other 'fudge' I'm supposed to be mixing in to mouse locations while a drag operation is underway? My fix suggests otherwise, as I'm able to ascertain correct positions of items manually in mouseDragged with only the 'normal' transformation of window-to-view coords, but I'm curious as to what you mean about the fudge-factor.
I just meant, if you recreate the tracking areas at some point(s) during the autoscroll and they behave *as if* they're in the unscrolled position, then you could try offsetting their bounds by the distance between the right and wrong positions, so that they behave *as if* they were where you wanted them to be. (And then fix them later.)
But maybe it's a lame idea. _______________________________________________ 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 arch...@mail-archive.com
