Re: Nib Dependency Madness
Re: Nib Dependency Madness
- Subject: Re: Nib Dependency Madness
- From: Andrew Merenbach <email@hidden>
- Date: Wed, 27 May 2009 11:01:08 -0700
On May 27, 2009, at 10:04 AM, Waldo Lee Sharvey wrote:
I have an pre-ib 3.0 nib that makes use of a control in a
custom-written palette that a previous programmer seems to have lost.
Whenever I try to open the nib in Interface Builder 3.0, I get a
dialog with the message "Unable to resolve plug-in dependency for
mynibfile.nib". The warning dialog does give me the option of
"Continue" which I'd think would let me continue to open the nib sans
the control, but this only leads to another dialog stating "The
document mynibfile.nib" could not be opened. An instance of
mypalettecontrol could not be decoded". And IB stops dead in its
tracks.
My goal is to salvage/reuse what's left of the nib file keeping
everything intact, with the exception of the problematic palette
control, which I don't really care about anyways. Is this possible, or
is the entire nib file basically fried by virtue of this dependency
and not being able to decode a palette that no longer exists?
You won't be able to open the old file in Interface Builder 3. Try
installing Xcode 2.5, then opening it in Interface Builder 2, then
creating a new nib and copying over the interface from the old one,
then save the new nib and start using it in IB 3 (how's that for a run-
on sentence?).
Cheers,
Andrew
_______________________________________________
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