Dennis,
Well, it might be far from ideal for CD performance, but that doesn't
mean it's bound poorly. It is done exactly to do what we need it to
do, otherwise this binding would have been the first to be targeted
for rewrite.
Creating a gigantic autoreleased NSArray from valueForKeyPath:
On 29 Mar 2008, at 06:29, Ron Lue-Sang wrote:
There's also the controller attribute Always Use Multi Value
Marker which will keep the controller from even looking at the
property values of the selected objects as long as more than one
object is selected in the controller.
Of course,
The problem I'm having arises when selecting all images at once
(Command+A), if they are fairly large in number (in my store: ~2000).
This takes an enormous time that is definitely O(n).
Command-A should be instantaneous, even for selections 10x larger.
The typical performance problems I've
On 28 Mar 2008, at 20:24, Ben Trumbull wrote:
The problem I'm having arises when selecting all images at once
(Command+A), if they are fairly large in number (in my store: ~2000).
This takes an enormous time that is definitely O(n).
Command-A should be instantaneous, even for selections
On Mar 28, 2008, at 7:38 PM, Dennis Lorson wrote:
On 28 Mar 2008, at 20:24, Ben Trumbull wrote:
The problem I'm having arises when selecting all images at once
(Command+A), if they are fairly large in number (in my store:
~2000).
This takes an enormous time that is definitely O(n).
On Mar 28, 2008, at 10:08 PM, Ben Trumbull wrote:
Binding to .selection.a is going to call -valueForKeyPath:@a on
the array that's selected, which is 10,000 objects. Since the text
field can only show one of those values, this is kinda pointless.
This is the source of the recursion.
