On Mar 30, 2018, at 12:22 , Richard Charles <rcharles...@gmail.com> wrote: > > My custom view implements -[NSResponder mouseDragged:] but this has never > caused any problems.
I don’t have much to suggest except “try stuff”. I’d try to see what happened if I commented out the “mouseDragged” override, if I commented out its contents (so that it swallowed the event), and if I commented out its contents but added [super mouseDragged: event] to pass the event up the chain. I wonder if the message reflects the amount of time your mouseDragged is taking to handle the event? Maybe 112.994 is “harmful" only because it’s detected that your code can’t handle that many per second. It’s also possible that message is something you can validly ignore. Does it happen in a release build, too? Lastly, what kind of input device is producing these rates? Is it a mouse or a trackpad or something else? There might be something to chase after in that direction. _______________________________________________ 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
