Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Why use NSObjectController?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why use NSObjectController?

Subject: Re: Why use NSObjectController?
From: mmalc crawford <email@hidden>
Date: Sun, 10 Aug 2008 22:14:31 -0700


On Aug 10, 2008, at 10:08 PM, Seth Willits wrote:

On Aug 10, 2008, at 9:54 PM, mmalc crawford wrote:

What is it that NSObjectController offers me?
An implementation of the NSEditor and NSEditorRegistration protocols.

Ah.
Now I'll just have to figure out when I'd want to use those...

Any time you want to ensure that pending edits in the view layer are committed to your underlying model objects -- for example, if the user has entered a new value in a text field then saves a document before "exiting" the field (and causing the change to be committed).

mmalc

_______________________________________________

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: Why use NSObjectController?
From: Seth Willits <email@hidden>


References:  
  >Why use NSObjectController? (From: Seth Willits <email@hidden>)
  >Re: Why use NSObjectController? (From: mmalc crawford <email@hidden>)
  >Re: Why use NSObjectController? (From: Seth Willits <email@hidden>)




Prev by Date:
Re: Why use NSObjectController?

Next by Date:
Re: Does [NSApp setApplicationIconImage] leak memory?

Previous by thread:
Re: Why use NSObjectController?

Next by thread:
Re: Why use NSObjectController?

Index(es):

Date
Thread