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".
I probably spoke out of place to say "most of AppKit". The code I
modeled could well be legacy AppKit behavior.
Some of the tracking PDFView does is in fact akin to button tracking
(link annotations are the obvious example). Text selection though
perhaps is better split across the multiple events. A hybrid approach
like that though might have been even worse for sublclassers. I don't
know.
john calhoun—_______________________________________________
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
