Re: NSTreeController Problem
Re: NSTreeController Problem
- Subject: Re: NSTreeController Problem
- From: "Jeffrey J. Early" <email@hidden>
- Date: Wed, 9 Nov 2005 12:31:58 -0800
Austin,
I actually posted the same problem on the omni-dev list on Nov. 6th
as well and have come up with a work around since then. All I had to
do to make things work was implement the optional "Count key path" of
NSTreeController and things worked again. Hopefully that can work for
you as well...
I am having trouble consistently reproducing this bug in a second,
simpler, test project -- but there must be something to it being that
two of us independently reproduced the same problem...
Jeffrey
BTW - Here's the start of the relevant thread:
http://www.omnigroup.com/mailman/archive/macosx-dev/2005-November/
057828.html
I believe I have found a bug in NSTreeController that is seemingly
isolated to 10.4.3:
I recently picked up a test project I had started a few weeks ago
prior to the release of 10.4.3. Basically, there is a table and an
outline -- an array controller and a tree controller. The table is
responsible for a source list of sorts, and then the outline displays
stuff inside the selected source item. This all works well and
good... until you do the following:
Let's say there are 3 items in the source list: Item One, Item Two,
Item Three. Item One contains 4 things to be displayed in the outline
view, Item Two contains 6 things, and Item Three contains 8 things.
If I select Item One, then Item Two, then Item Three, everything
works as fine. The outline updates with the necessary items. Now, If
instead I select Item Two then Item One, or Item three then Item Two,
I get an out of bounds error. The problem, thus, apparently is caused
by updating the tree controller with a lower number of items than the
previous selection in the source list.
The error looks something like this:
*** -[NSCFArray objectAtIndex:]: index (4) beyond bounds (4)
The outline properly updates with the items in the selected source
list, but it locks up and then crashes if I click anywhere.
I realize the description is kind of vague, but it's a rather
specific problem. If anyone understands what I mean, has an idea as
to how to go about fixing it, or has experienced it themselves,
please speak up. Thanks a bunch for your time.
Austin Sarner
_______________________________________________
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