Re: NSCollectionView deselection
Re: NSCollectionView deselection
- Subject: Re: NSCollectionView deselection
- From: Thomas Davie <email@hidden>
- Date: Tue, 2 Mar 2010 15:52:03 +0000
On 2 Mar 2010, at 14:39, Markus Spoettl wrote:
> On Mar 2, 2010, at 3:36 AM, Thomas Davie wrote:
>>> On Mar 1, 2010, at 2:42 PM, Thomas Davie wrote:
>>>> However, when the user clicks on item B after clicking on item A, setSelected:NO is *not* sent to the NSCollectienViewItem subclass for A. This displeases me greatly :(.
>>>
>>>
>>> Works fine for me. Are you sure it's not called/set? Put a breakpoint into the setter into the setter of your NSCollectienViewItem subclass to find out.
>>
>> Hmm, that's exactly how I'm finding out that it's not being called :/
>
>
> Then it actually may not be deselected. Are you sure it is being deselected? What controls your selection? What is your binding setup? Do you have multi-selection enabled? Maybe something is wrong with the selectionIndexes of the NSArrayController which I presume provides the content of the collection view and the selection. You're not saying what your setup is like.
The NSCollectionView certainly *thought* it was being deselected – if the user clicks A, then A again, only one setSelected:YES gets sent, if the user clicks A, then B, then A again, setSelected:YES gets sent to A twice and B once.
I've worked around this now by writing an NSCollectionView subclass with my own selection and drag/drop code.
Tom Davie_______________________________________________
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