On Wed, Aug 8, 2012, at 10:38 AM, Corbin Dunn wrote: > No it hasn't changed, but the clicked row is set *after* you return a > menu. That way your menu validation code can use it. I think the > DragNDropOutlineView demo shows how to do this.
I've always thought this was an extremely odd design decision, since it essentially forces you to use a menu delegate to build your menu rather than just handing back the correct NSMenu instance from -menuForEvent:. Is there a reason that I shouldn't file a bug asking for clickedRow to be set as soon as the row is clicked? --Kyle Sluder _______________________________________________ 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
