• 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: NSArrayController nib binding vs code binding
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSArrayController nib binding vs code binding


  • Subject: Re: NSArrayController nib binding vs code binding
  • From: Kyle Sluder <email@hidden>
  • Date: Mon, 18 Jul 2011 20:02:44 -0700

2011/7/18 Trygve Inda <email@hidden>:
> I have a class (MyClass) that conforms to the collection methods for mutable
> collections such as...
>
> -(void)insert<Key>:(NSArray *)locationArray atIndexes:(NSIndexSet *)indexes

What happens if instead of implementing the collection methods, you
just expose the NSMutableArray as a property directly?

--Kyle Sluder
_______________________________________________

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: 
 >NSArrayController nib binding vs code binding (From: Trygve Inda <email@hidden>)

  • Prev by Date: Re: NSArrayController nib binding vs code binding
  • Next by Date: Re: NSArrayController nib binding vs code binding
  • Previous by thread: Re: NSArrayController nib binding vs code binding
  • Next by thread: Why are these objects still faults?
  • Index(es):
    • Date
    • Thread