Interface Builder Bug? Changing Outlet Name Breaks It Forever
Interface Builder Bug? Changing Outlet Name Breaks It Forever
- Subject: Interface Builder Bug? Changing Outlet Name Breaks It Forever
- From: Jerry Krinock <email@hidden>
- Date: Sun, 11 Dec 2005 15:36:57 -0800
- Thread-topic: Interface Builder Bug? Changing Outlet Name Breaks It Forever
I just want to see if anyone else has experienced this before I file a bug
report; I can't believe there is no mention of this in the archives:
I have aan outlet in the window controller (file's owner) wired to a control
object. I'm very fussy about my outlet names, and after changing the
function of this control slightly, I decide to change its name. So I change
its name in my Objective-C code, and in the class' outlets in Interface
Builder. I do not disconnect the control from the outlet, because I'm just
changing its name. I compile, link, run, and load the window all with no
errors indicated by compiler or console. BUT, the renamed control no longer
gets instantiated; its address is nil, and of course it doesn't work.
I try disconnecting and reconnecting; no good. I try getting new controls
from the palette and reconnecting them; no good. I try quitting and
relaunching IB; no good.
The only way to fix it is to start from scratch by adding an outlet of a
DIFFERENT name to the class and using it. It's as though this name gets
somehow blacklisted in the IB document, and just won't work any more. I've
had this happen with checkbox NSButtons and with NSImage/Views.
This has happened to me more than once; hasn't anyone ever seen it? It's
such a strange bug; maybe it somehow only happens if you're using
CodeWarrior, which I believe is rare nowadays with Objective C.
Jerry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden