It seems indeed they changed the internals, however PDFView doesn't
use NSCells and NSTrackingAreas are only for mousemoved events if I'm
not mistaken...
Alex
On 31-okt-2007, at 12:53, Thomas Engelmeier wrote:
On 31.10.2007, at 11:51, Alexander Griekspoor wrote:
Is it me or does it no longer work to subclass mouse events in
PDFView? mouseDown is called correctly in my subclass, but after
that I never receive mouseDragged and the mouseUp events. This
poses serious problems for what worked fine under Tiger (showing a
menu upon mouseUp). Is there a workaround or someway to know when
the user stopped selecting?
Is it related to the problem "Re: mouseUp: in TableView on
Leopard" ? As I cannot spot it on the list archives, here a summary:
*when* are you expecting it to be called? In NSTableView's
mouseDown,
it has always created a loop where it processed events. The mouse
logic has changed a bit to accommodate new features and bug fixes.
and
TableView will consume the mouse events when tracking from
mouseDown. You should use the "tracking" class of methods in the
NSCell, or the -action/-doubleAction for NSTableView if you want
to respond to a click or double click.
Maybe the PDFView was altered for similar reasons.
_______________________________________________
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
