• 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 problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTreeController problems


  • Subject: Re: NSTreeController problems
  • From: Charles Srstka <email@hidden>
  • Date: Sun, 18 May 2008 15:57:35 -0500

Thanks, that looks very useful. I only have one trepidation about it, which concerns this:

On May 18, 2008, at 3:33 PM, Jonathan Dann wrote:
- (NSArray *)rootNodes;
{
	return [[self arrangedObjects] childNodes];
}

Isn't -arrangedObjects one of those methods you're never supposed to call manually, only through bindings? At least, that seems to be the vibe I picked up while searching the list before posting my question. The docs say this:


Returns an proxy root tree node for the containing the receiver’s sorted content objects.

...


Prior to Mac OS X v10.5 this method returned an opaque root node representing all the currently displayed objects. This method should be used for binding, no assumption should be made about what methods this object supports.


which of course is nice and ambiguous. It says no assumption should be made, but says that in a paragraph prefixed by "Prior to Mac OS X v10.5". Since the root note was opaque and unreliable as to format prior to OS X v10.5, does that mean that it *can* be reliably used now that it is defined as an (sic) proxy root tree node for the (sic) containing the receiver's sorted content objects, or does that still apply?

Thanks,
Charles_______________________________________________

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


  • Follow-Ups:
    • Re: NSTreeController problems
      • From: Jonathan Dann <email@hidden>
References: 
 >NSTreeController problems (From: Charles Srstka <email@hidden>)
 >Re: NSTreeController problems (From: Jonathan Dann <email@hidden>)

  • Prev by Date: Re: releasing NSKeyedUnarchiver causes crash
  • Next by Date: Cocoa et al as HCI usability problem
  • Previous by thread: Re: NSTreeController problems
  • Next by thread: Re: NSTreeController problems
  • Index(es):
    • Date
    • Thread