> On 10 May 2015, at 2:26 pm, David Durkee <da...@dwdurkee.com> wrote: > > Although this can be a pain if the control is in a view that also scrolls. I > think some Adobe applications have this issue.
Many apps do, because of the way NSResponder works by passing unhandled events to the next responder. It happens with any nested scroll views, or any other view that implements the -scrollWheel: method. I’m not sure if there’s any way to resolve it, because the target of a scroll wheel event is given solely by its frame, not whether it’s key, etc. One way would be to require a modifier key, but since that’s it's widely implemented that way, it isn’t very discoverable. —Graham _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
