Re: selectionIndexesForProposedSelection on mouse Up or mouse Down
Re: selectionIndexesForProposedSelection on mouse Up or mouse Down
- Subject: Re: selectionIndexesForProposedSelection on mouse Up or mouse Down
- From: Corbin Dunn <email@hidden>
- Date: Mon, 16 May 2011 16:29:27 -0700
On May 13, 2011, at 10:56 AM, Quincey Morris wrote:
> On May 13, 2011, at 10:36, Corbin Dunn wrote:
>
>> On May 12, 2011, at 1:42 PM, Brad Stone wrote:
>>
>>> I put in NSLog calls to show me when "proposed" and "didChange" get called. NSTableView's delegate gets called on mouseDown while NSOutlineView on mouseUp.
>>
>> That shouldn't be true...and I'm not sure I believe it. Do you have a backtrace showing this case?
>
> I was able to confirm the difference in behavior that Brad observed, but I didn't try to find the cause.
>
> In the example I looked at, there were two implementation differences between the table and outline view:
>
> -- The outline view data source implements 'outlineView:writeItems:toPasteboard:' (etc), while the table view data source does not implement 'tableView:writeRowsWithIndexes:toPasteboard:' (etc).
>
> -- The outline view delegate implements 'outlineView:selectionIndexesForProposedSelection:', while the table view (which dates back to older code) uses 'tableView:shouldSelectRow:'.
>
> I'm guessing one of these causes the difference in behavior, most likely the first.
>
That is correct -- if you implement drag, then things are delayed slightly to allow the drag to start. But, the ordering is identical for tableview and outlineview, if implement the same delegate/datasource methods.
corbin
_______________________________________________
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:
This email sent to email@hidden