> >> I’d say the best solution is the one that Ken described. Implement the >> to-many >> accessors such as countOf<property>, objectIn<property>AtIndex:, >> insertObject:in<property>AtIndex:, and so forth. Then the underlying storage >> can be an NSDictionary, a skip list, or whatever you want, and as long as >> your >> accessors are abstracting it away properly, the rest of your code will >> neither >> know nor care what is actually being used to store your data. > > I have done this and it works nicely except... > > I only allow one item in my NSArrayController / NSTableView to be selected. > If I use the mouse to click and drag off the edge of the NSTableView it > scrolls fine, but if I use the keyboard, I am able to move the selection off > the edge of the table... The selection moves ok, but the table doesn't > scroll to keep the selection visible. > > Any idea why?
Nevermind... Sending something to the wrong object in my selection-changed code. T. _______________________________________________ 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]
