What it sounds like you're really asking in the latest part of this thread is for every object in a given runtime to track the messages called upon it with a time stamp in order to compare those for an exact ordering of calls conducive to your needs.
That COULD be useful, but it would be really resource-intensive, especially in a heavy-object-usage process if turned on for every object, but it could be turned on only for objects of a particular class in your scenario. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ On Feb 15, 2012, at 8:12 AM, Sean McBride <[email protected]> wrote: > On Tue, 14 Feb 2012 21:08:38 -0800, Kyle Sluder said: > >>> Are you calling -type on the events you are receiving? Checking that >> value should make it clear whether the event you have received is a >> mouse event or not. If not, and you need the mouse location, you can >> get if from NSEvent's +mouseLocation or a relevant window instance's - >> mouseLocationOutsideOfEventStream. >> >> The question is whether any debugging code can be added to catch >> instances where -type isn't being called before asking for the mouse >> location. > > And since no one has said "yes", I've assumed it's "no" and filed > <rdar://10868211> with the suggestion. > > In the meantime, I'll create a category method that wraps locationInWindow > and delegates to mouseLocation or similar otherwise. > > Thanks to all who replied, > > -- > ____________________________________________________________ > Sean McBride, B. Eng [email protected] > Rogue Research www.rogue-research.com > Mac Software Developer Montréal, Québec, Canada > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
