Re: hosed IBOutlets
Re: hosed IBOutlets
- Subject: Re: hosed IBOutlets
- From: Vince DeMarco <email@hidden>
- Date: Mon, 21 Feb 2005 09:58:27 -0800
On Feb 19, 2005, at 5:10 PM, Paul Forgey wrote: Well apparently I was inadvertently overriding a method. I had a method in my class called setProgress: which would update the controls appropriately. Upon more careful inspection in the debugger, I saw it was being called by the App Kit internals while unpacking the nib. Couldn't find any documentation about that method anywhere throughout the entire class hierarchy or protocols. Renamed it to something else and everything suddenly began working again.
Objective-C is simple, but sometimes it is too simple.
Please look at the IB FAQ from the FAQ
• How are outlets connected at runtime?
The runtime code will use the list of outlets you generated in IB at design time. For example, if you had specified an outlet called foo, IB will first investigate the target class to see if it responds to setFoo:(id). If it does, that method is called with the contents for foo. If setFoo:(id) doesn't exist, the instance variable foo itself is filled with the contents for foo.
Yes this is hard to find, but if you look under Help menu in Interface Builder there is lots of good info there.
Vince
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden