Re: NSCollectionView deselection
Re: NSCollectionView deselection
- Subject: Re: NSCollectionView deselection
- From: arri <email@hidden>
- Date: Wed, 13 Jul 2011 10:35:00 +0200
i was struggling with this, when i happened to stumble across a remark
from someone on the cocoadev-forums that hit the nail right on the
head:
" … Also, you didn't call super's -setSelected: within your override … "
http://cocoadev.com/forums/discussion/comment/2190#Comment_2190
So, in your implementation of setSelected: in your
NSCollectionViewItem-subclass, also call [super setSelected:..]
Something to easily overlook.
g
arri
On Tue, Mar 2, 2010 at 8:25 PM, Markus Spoettl
<email@hidden> wrote:
> On Mar 2, 2010, at 10:52 AM, Thomas Davie wrote:
>> 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.
>
> You shouldn't need to work around this because this just works when everything is set up correctly. The fact that it doesn't work for you indicates that there's something wrong with your setup. You don't give any details on how everything is set up in your case.
>
> Regards
> Markus
> --
> __________________________________________
> Markus Spoettl
>
>
> _______________________________________________
>
> 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
>
_______________________________________________
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