Doh! You're right if course. How about using removeSelectedIndexes:?
Should be faster than sorting the contents before removing them,
Thanks.
'removeObjectsAtArrangedObjectIndexes' does the job nice and quickly.
___
Cocoa-dev mailing list (Cocoa-dev
On Mon, Mar 24, 2008 at 10:35 AM, Jeff LaMarche <[EMAIL PROTECTED]> wrote:
> Doh! You're right if course. How about using removeSelectedIndexes:?
> Should be faster than sorting the contents before removing them,
Hrm. Why not try attacking this from the model end instead of the
controller end?
Doh! You're right if course. How about using removeSelectedIndexes:?
Should be faster than sorting the contents before removing them,
Sent from my iPhone
On Mar 24, 2008, at 10:26 AM, Martin Linklater <[EMAIL PROTECTED]>
wrote:
I would think that
[itemBrowserArrayCTRL removeAllObjects];
I would think that
[itemBrowserArrayCTRL removeAllObjects];
would be your best. By calling arrangedObjects and feeding it to
removeObjects:, you're causing your array to sort all 15000 entries
before it removes them individually.
NSArrayController doesn't have a removeAllObjects method...
I would think that
[itemBrowserArrayCTRL removeAllObjects];
would be your best. By calling arrangedObjects and feeding it to
removeObjects:, you're causing your array to sort all 15000 entries
before it removes them individually.
HTH
Jeff
On Mar 24, 2008, at 10:16 AM, Martin Linklater wrot
