On 21/07/2009, at 4:07 PM, Alexander Bokovikov wrote:
- rename the Object Controller instance, i.e. click on the "Object"
name label below the blue cube, causing its inline editor
appearance, and type something. I used "AppController" name.
- DO NOT change "NSObject" class name at the top of Info page of the
Inspector.
[...]
- CHANGE the AppController object instance CLASS NAME to
"AppController" (was NSObject) in the Object Inspector; the action,
we just created DISAPPEARS, so "Actions panel is EMPTY.
This might be the cause of the problems you had (possibly could still
be considered an IB bug) as it's not a workflow that really makes much
sense.
The name of an object in IB is just a crutch for the programmer, not
an important aspect of the object's properties. So changing the name
does nothing, really. What really matters is the class of the object,
set in the Inspector. Change that FIRST, and it so happens to also
change the name for you, but the reverse is NOT true. Once you have
the class set properly, it will know which source file header it needs
to read to load the relevant actions and outlets, and will presumably
manage them in a bug-free manner from then on - e.g. if you delete an
outlet in the header, it will be indicated as a missing outlet in IB
and allow you to delete it.
Setting the name automatically when you set the class is a
convenience, but equally you can change the name to make it clear to
you what the object is. The name has no effect on anything.
--Graham
_______________________________________________
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
