On Tue, 18 Oct 2011 11:00:49 -0700, Eeyore eey...@monsterworks.com said:
When I declare something as an IBOutlet, am I exposing it to others?
IBOutlet is not a declaration in any meaningful sense. It's just a bit of
internal fluff with Xcode; the compiler never sees it. It makes no difference
On Sun, 16 Oct 2011 13:53:05 -0700, Eeyore eey...@monsterworks.com said:
I noticed that I many of my IBOutlets were only being used to modify the view
from the viewDidLoad methods but which were not accessed later in my code.
These outlets exist so that I can keep consistent appearance settings
Thanks Matt, was kind of hoping you would provide some insight (your responses
to others have been helpful).
Very ingenious, but doesn't it leave a lot of stuff lying around that is just
an accident waiting to happen? You are assuming that setLabel: will be called
only by the nib-loading
I don't quite understand your special situation. Both your old and new
style accessors look weird. But the new is definitely better. Go for it.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
Thanks,
I guess the situation is that I really want a writeonly property. I don't ever
need to read the outlet, I just want to do some adjustments when the property
is first set (in this situation, when the nib is loaded).
The old style shouldn't look too weird. It is just using @synthesize to
I noticed that I many of my IBOutlets were only being used to modify the view
from the viewDidLoad methods but which were not accessed later in my code.
These outlets exist so that I can keep consistent appearance settings in a
large number of nibs without actually editing each nib. As a
