Re: NSTableview datasource issues
Re: NSTableview datasource issues
- Subject: Re: NSTableview datasource issues
- From: Greg Guerin <email@hidden>
- Date: Sun, 20 Dec 2009 19:13:04 -0700
I understand your proposition. For some reason, the spaces are
stripped off by the e-mail system, but you got it right.
Did your email system also capitalize ObjectValueForTableColumn?
Actually, segmentDict contains the copy of a global dictionary
created by the method [[MyDocument getSectorSegmentData:(id)
sender] > mutableCopy]. Unfortunately i cannot give here all the
code. Also, when I print the datasource and delegate for
segmentTableView, it is clear that it is not nil: the log shows
SelectorController, which is what it should be.
My major puzzle is that all other TableView in the application
using different datasources get loaded. Cleaning all targets does
not change anything.
Brief, the major problem is this: the datasource methods do not get
called.
Datasource is not nil at run time, no error in the code. The
ArrayController is not empty, the code looks fine.
I will go back and review for the thousandth time the code from
scratch and all the bindings, but up to now, I can't figure out
what is wrong.
Maybe you can add some assertions in your code. For example, given
the way segmentDict is used, it strongly suggests your design is
effectively a singleton. That is, there must only be a single
instance of SelectorController created and init'ed.
The other thing that occurred to me is if an instance of
SelectorController is recreated by the nib, and another instance is
created in your code, then the instance you see with valid datasource
and delegate may not be the instance that the nib is using. One
instance may not be getting completely initialized.
As a last resort, try stripping classes, xibs, etc. in order to
produce a simplified test case that still exhibits the problem. In
the process of simplifying, sometimes you do something that causes
the problem to go away. Tracking down the change that causes things
to work then leads to identifying the cause of the problem. Even if
the simplified case still has the problem, you still have something
that others can run and help debug.
-- GG
_______________________________________________
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