On Wednesday, October 31, 2007, at 11:33AM, "Murat Konar" <email@hidden> wrote:
>
>On Oct 31, 2007, at 10:47 AM, John Calhoun wrote:
>
>> Most of AppKit in fact don't use the -[mouseDragged] and -[mouseUp]
>> events for tracking.
>
>Really? Outside of things like buttons, that's an unfortunate choice,
>isn't it? As the "Cocoa Event-Handling Guide" points out, a class
>that handles dragging in this manner is "more difficult to extend
>without the subclass reimplementing all the dragging code".
>
>You'd think that extending AppKit classes would be a fairly common
>thing to want to do...
I prefer using the NSResponder methods because it doesn't foul up other event handling, and I thought that's what Apple people on this list have advocated (but my memory may be faulty). I recently discovered that NSSplitView's mouseDown: breaks mouseDragged: for subviews...which seems particularly odd since NSSplitView is useless without subviews. I wish there were a coherent story on this from Apple. If the frameworks force us to use while(1) loops, then just remove mouseUp:/mouseDragged: from NSResponder and be done with it.
--
adam
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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/email@hidden
This email sent to email@hidden
