Single bottleneck for all Array controller selection changes?
Single bottleneck for all Array controller selection changes?
- Subject: Single bottleneck for all Array controller selection changes?
- From: Matt Gough <email@hidden>
- Date: Thu, 15 Jun 2006 13:22:47 +0100
In my subclass of NSArrayController I have been overriding
setSelectionIndexes: to filter certain selection changes. This has
been working fine up until now as the calling code has only been
using setSelectionIndexes: or setSelectingIndex. Both of these go
through my override.
However I just started using setSelectedObjects from my calling code
and noticed that this doesn't call down to setSelectionIndexes:.
Obviously I could just override all of the selection changing
methods, but that would require me to keep up to date with any
additions to future versions of NSArrayController.
Is there any single bottleneck that all of the Array controller
selection changing goes through. If not, what is the minimum set of
methods I should override to be fairly future-proof.
Matt Gough
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden