• 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: IB key-value oddity...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IB key-value oddity...


  • Subject: Re: IB key-value oddity...
  • From: "John C. Randolph" <email@hidden>
  • Date: Wed, 13 Jun 2001 12:06:42 -0700

On Wednesday, June 13, 2001, at 09:47 AM, Fritz Anderson wrote:

At 6:54 AM -0700 6/13/2001, Henri Lamiraux wrote:
The rule for outlet connection is as follow:

If you have an outlet foo, first we look for a -setFoo: method and call
it if it exists passing the outlet value as parameter. If this method
doesn't exist we them look for a instance variable foo and set it
directly.

It is a very good rule, sensible, elegant, and easy to understand. It wasn't even hard to infer.

I just don't remember having seen it before.

My question was honest, and I renew it: Where was this rule documented? When I find a gap like this in my knowledge, I want to go to the source to see if there are other gaps I might fill. I wouldn't ask anyone to go looking for it, but if someone on the list can remember where they saw this rule, I'd appreciate the pointer.

I don't know if it's documented currently, but I remember reading it in the AppKit docs back in the NeXTSTEP days, probably under -loadNibSection:owner: (which doesn't exist in OpenStep)

As I recall, in earlier versions nib loading could *only* make connections if there was an accessor method. It wasn't able to look up ivars by name.

-jcr


Support your right to protest a criminal nut-cult. http://freehenson.da.ru/


References: 
 >Re: IB key-value oddity... (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Cocoa, a complete Mac OS X API?
  • Next by Date: Getting HTML
  • Previous by thread: Re: IB key-value oddity...
  • Next by thread: Re: IB key-value oddity...
  • Index(es):
    • Date
    • Thread