Okay, I see them now. I was missing them in the rather long list of
outlets (over 130!) for the main controller.
I wanted to understand this better because I want to re-factor the
code so that there are NOT 135 outlets for one controller. Currently
we have two windows that handle different tasks, but share the
controller. I want separate controllers for each window/task.
Thanks, Ken.
On Jun 13, 2008, at 6:22 PM, Ken Thomases wrote:
On jun 13, 2008, at 4:21 PM, Paul Archibald wrote:
This puzzles me. I am tracing through some code in which I am
looking at the value of some selected popup menu items. I am
seeing the correct values for them, but I have to confess I don't
know how the code is connected to the popup, or just why the code
even works! I see the connections for the buttons on the
interface, and I hit the breakpoints I expect, but I don't see any
connections between the member variables and the popup items.
There are instance vars for the popups in the code, but I don't
see how they are connected to the NIB.
It sounds to me like you're not familiar with "outlets", which is a
pretty basic part of Cocoa GUI design. You probably need to review
the conceptual documentation:
http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaFundamentals/
http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaFundamentals/CommunicatingWithObjects/
chapter_6_section_3.html#//apple_ref/doc/uid/TP40002974-CH7-SW3
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [EMAIL PROTECTED]
