> On May 24, 2016, at 23:45 , Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On May 24, 2016, at 23:26 , Rick Mann <rm...@latencyzero.com> wrote: >> >> Eh, I think I'll just use my current workaround using NSOutlineView methods. > > Really? There’s nothing wrong with using ‘selectedObjects’. The only drawback > is that it has to create an actual NSArray each time you ask for it, but > that’s not a meaningful performance penalty in most situations. > > Another alternative is to bind the tree controller’s selectionIndexPaths > binding to a property in your view/window controller. In effect, that binds > the outline view’s selection *through* the tree controller to your property. > Because it’s maintained by a binding, the property will be KVO compliant, or > you can use the ‘outlineViewSelectionDidChange:’ delegate method. (The > difference is that the delegate method is not invoked for *programmatic* > changes of the selection.)
Oh, that sounds like the right solution. Thanks! -- Rick Mann rm...@latencyzero.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
