• 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: 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: "R.L. Grigg" <email@hidden>
  • Date: Mon, 11 Aug 2008 11:05:58 -0700


On Aug 11, 2008, at 8:52 AM, Sean McBride wrote:

But it seems you can't
send commitEditing to a textfield.

Why? If this was supported, wouldn't it greatly simplify things, meaning no need to have a NSController subclass, etc.? This is what confuses alot of newbs like me. Not arguing against it, just trying to see the motivation behind it.


Russ

_______________________________________________

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: Mike Abdullah <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>)
 >Re: Why use NSObjectController? (From: "Sean McBride" <email@hidden>)

  • Prev by Date: Re: NSConditionLock vs MPQueue
  • Next by Date: Re: Newbie Question on "self"
  • Previous by thread: Re: Why use NSObjectController?
  • Next by thread: Re: Why use NSObjectController?
  • Index(es):
    • Date
    • Thread