Bill Cheeseman corrected/educated me:
On Sep 23, 2009, at 7:11 AM, Gregory Weston wrote:
There is no mechanism in the current version of the tools for
defining outlets and actions in IB; only for assigning them.
I don't believe this statement is true, if I understand your point
correctly. Here's how to create an outlet or an action in IB 3.2 and
write it back to your source files. You can also create wholly new
classes this way.
1. In any of your project's nib files, go to the Library window (not
the Inspector window) and select the Classes tab. Using the pop-up
menu at the top, select one of your project's classes in the very long
and awkward hierarchical menu. For example, your class MyDocument
would appear in the menu under NSDocument if it inherits from
NSDocument.
You know what? I had never noticed that. I still think the OP is
confused, though, about where he was supposed to be looking for things.
Is this less than what you used to be able to do in IB? To the best of
my memory, it gives you more control over what is produced.
Offhand, I don't think it's more or less functionality or control than
I remember. But at least for me it was less obvious. I switched over
to defining things by hand when 3.0 came out because I found it
easier. Or perhaps I should say "more easily."
_______________________________________________
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
