on 3/6/08 6:50 AM, [EMAIL PROTECTED] purportedly said: > Since most of what I write supports quite old Mac OS X versions, I'm > only just now starting to experiment with CoreData and I've run into > a stumper fairly early. I've got a window with 2 NSTableView objects > on it. One was created by dragging an entity from the data model into > the window and letting IB create a multi-object view. The second was > created manually (still in IB, I don't mean in code) and has a single > column bound to one of the same fields as is the first table through > the same array controller. The generated table is about 4.5 rows > tall, while the one I made can show about 13 rows. My data set has 10 > entries. > > Now here's the problem. My manually-created table only shows the > correct value for a row once it has been displayed in the generated > table. So on launch I can see the correct data for the first 5 rows, > and the remainder are zeroes. Logging awakeFromFetch confirms that > the latter rows haven't been read. As I scroll the generated table, > the values will fill in in the table I created. > > I've compared every facet of the tables I can think of, but obviously > there's a difference I'm missing. Any pointers regarding what that is > would be appreciated.
I don't know if NSArrayController supports being bound from two different "collection-type" views. You probably need a separate controller, either bound in the same way as the first (to the managed object context) or bound to the first array controller. Best, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
