• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSTreeController and NSTreeNode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTreeController and NSTreeNode


  • Subject: Re: NSTreeController and NSTreeNode
  • From: Sam Stigler <email@hidden>
  • Date: Tue, 20 Nov 2007 01:59:55 -0800

Amen to that; as I recall a major problem with the pre-Leopard NSTreeController was that it didn't provide any access to the actual objects in the tree... just proxies. (One would think this is how it should be with MVC, but there are circumstances in which it is very useful to know which node is selected in the view.) This led to difficulties when trying to manipulate objects represented by nodes in a tree. People (myself included) came up with convoluted workarounds to try to gain access to the actual observed objects. (See, for example, http://theocacao.com/document.page/130 and its comments.)

The NSTreeController release notes for Leopard (http://developer.apple.com/releasenotes/Cocoa/AppKit.html#NSTreeController ) detail the (extremely helpful!) changes made to remove the need for such workarounds.

-Sam


On Nov 20, 2007, at 12:25 AM, Rob Keniger wrote:


On 20/11/2007, at 5:42 PM, norio wrote:

I'm looking at SourceView sample. This is nice example but it doesn't run on 10.4.

I'd like the app run on 10.4. For the purpose, would you tell me the following things?

1. Is NSTreeController's selectedNodes the same as NSTreeController's selectedObjects?

2. How do you implement functions for 10.4, instead of using NSTreeNode class which is introduced on 10.5?

I do especially like to know how to implement codes like NSTreeNode's parentNode and indexPath.


Having spent a lot of time working with NSTreeController on 10.4 I can tell you that if you want to use it for anything more than very basic things, you will find that it is buggy, unreliable and many of the features are only available in private methods.

Leopard's implementation is a dream in comparison and if you want to do extensive work with NSTreeController then if possible I highly recommend targeting Leopard. You will not regret it.

--
Rob Keniger

_______________________________________________

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

_______________________________________________

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


References: 
 >NSTreeController and NSTreeNode (From: norio <email@hidden>)
 >Re: NSTreeController and NSTreeNode (From: Rob Keniger <email@hidden>)

  • Prev by Date: Re: How to know OS Version
  • Next by Date: c++ and cocoa
  • Previous by thread: Re: NSTreeController and NSTreeNode
  • Next by thread: Re: NSTreeController and NSTreeNode
  • Index(es):
    • Date
    • Thread