On May 10, 2010, at 6:07 PM, Tom Hohensee wrote:
> Yes it is kind of odd. When I moved on from C to Objective-C and Cocoa I
> found there are many disconnects in the documentation. More specifically, IB
> and class documentation seems to not tie in very well just as you are
> pointing to in you question. I always figured it was because some concepts
> (and classes) where so broad and complex that it is best to limit the scope.
> As to why it is not in the header files? I cannot specifically recall any
> class header files that list the built in outlets.
> Anyway, very early on I got into the habit of checking for built in outlet in
> IB first then googling from there if needed.
>
> Tom
>
> On May 10, 2010, at 7:31 PM, Matt Neuburg wrote:
>
>> I've been thinking about how to explain to a beginner that some classes have
>> built-in outlets, and it strikes me that the documentation falls down here.
>> For example, you know and I know that a UIViewController has a view outlet;
>> it is visible in the Connections inspector in IB when you select an object
>> that's a UIViewController (or a subclass thereof). But the UIViewController
>> class documentation never mentions this fact; and neither does the header,
>> if it comes to that. Doesn't this strike you as kind of odd? m.
As I said, it's listed under Properties in the documentation.
And in UIViewController, the .h file declares an instance variable:
UIView *_view;
and the @property declaration declares it thus:
@property(nonatomic,retain) UIView *view;
Cheers,
. . . . . . . . Henry
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
