Hi Tony
> Ok, here is the magical answer as to why the remove: didn't work. Nice
> little warning in the Cocoa Bindings Programming topic:
>
> Warning: Providing the count key path to an NSTreeController instance
> disables the add:,addChild:, remove:, removeChild:, orinsert: methods.
>
> My
Ok, here is the magical answer as to why the remove: didn't work. Nice little
warning in the Cocoa Bindings Programming topic:
Warning: Providing the count key path to an NSTreeController instance disables
the add:,addChild:, remove:, removeChild:, orinsert: methods.
My object implemented a me
As he stated, -remove: does work, but its result is deferred.
On 15 May 2010, at 03:56, Tony Romano wrote:
> Thanks Quincey.
>
> removeObjectAtArrangedObjectIndexPath works but remove: still does not. It
> should remove the object, if there is a bug then I will file a bug report.
> anyone ha
Thanks Quincey.
removeObjectAtArrangedObjectIndexPath works but remove: still does not. It
should remove the object, if there is a bug then I will file a bug report.
anyone have ideas as to why remove: may not be working. I hate to find another
way and drop a possible issue/bug. Thanks.
-T
On May 14, 2010, at 15:39, Tony Romano wrote:
> I have a NSOutlineView bound to a NSTreeController in class mode(i.e. each
> NSTreeNode represents my Node object). Everything up to now is working fine.
> I am trying to remove a single node in the outline view by calling
> [outlineView remove:
