Re: IBOutlet not 'sticking' at runtime
Re: IBOutlet not 'sticking' at runtime
- Subject: Re: IBOutlet not 'sticking' at runtime
- From: Adam Raney <email@hidden>
- Date: Wed, 7 Sep 2005 21:32:17 -0500
Well I seem to have figured out the problem here. It seems that
having an instance variable named "target" was throwing something out
of whack. I guess there was a private variable with the same name
somewhere in the class chain.
I changed the name to ttarget to test the problem (leaving the method
still - (NSTextField *) target; ), and all works fine.
On Sep 7, 2005, at 8:43 PM, Adam Raney wrote:
Thanks for your help guys but so far no go.
The only custom method the class has (so far), is a getter method that
should just return the NSTextField reference. I have made sure that
"target" is not set programatically either, so it should not be
getting reassigned to nil.
I am running my program under debug, and have a breakpoint attached to
a button so I can check the "target" by calling the - (NSTextField *)
target; method. (which is simply "return target"). Stepping into the
script, I enter the custom instance, and see target set to 0x0, well
after awake from nib is completed.
I am still puzzled on this one. Any other ideas?
On 9/7/05, SA Dev <email@hidden> wrote:
[private / off-list reply]
Most likely you are setting your outlet to nil somewhere in your
code. Say you created an outlet called "myTextField" and connected
it. If at any time during runtime you say myTextField = nil; you're
killing the connection.
Hope this helps.
- SADev
On Sep 7, 2005, at 11:28 AM, Adam Raney wrote:
Hello all,
I have created a custom subclass of NSPopUpButton (ACRPopUpButton)
and given it an IBOutlet called target, typed to NSTextField.
In Interface builder, I have successfully placed the custom object
in my window (placed NSPopUpButton and selected ACRPopUpButton from
it's Custom Class option). I have also connected the target
IBOutlet to a text field on the same window.
The problem I have is, when the my app runs, the target is showing
up as 0x0, as though it is not getting assigned. This has worked on
other custom subclasses (such as my window controller), what could
be causing this issue?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40silentalcove.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden