Re: Interface Builder can't identify plugins when opening old NIBs
Re: Interface Builder can't identify plugins when opening old NIBs
- Subject: Re: Interface Builder can't identify plugins when opening old NIBs
- From: Jens Miltner <email@hidden>
- Date: Mon, 12 Nov 2007 09:34:40 +0100
On 10.11.2007, at 13:27, Ricky Sharp wrote:
On Nov 10, 2007, at 2:37 AM, Jens Miltner wrote:
I've rewritten our old IB palettes as Interface Builder plugins for
the new Leopard Interface Builder.
However, whenever I open a NIB file that was generated by the old
Interface Builder, containing some of our custom objects that
require the plugin, IB will tell me it can't find the appropriate
plugin, asking me to locate it.
My new plugin is definitely loaded in IB and when I press
"Continue" (without locating the plugin), the NIB loads just fine
and I can edit our custom objects properties, so I don't really
understand why IB insists on not being able to locate the plugins?
I also tried to save the NIB once with the new IB, but when opening
it again, IB will still prompt me for the plugin.
How can I make sure IB will associate my new plugin with the custom
objects stored by the old IB?
I have also seen this issue. One "solution" is to save the nibs in
the new 3.x format (I tried the 3.x NIB; I'll assume it will also
work for 3.x XIB).
Of course the problem in saving in 3.x format is that you'll no
longer be able to edit the NIBs with IB 2.x should you have the need
to. Fortunately, that wasn't an issue for me.
Unfortunately, that _is_ an issue for us :(
I too have seen no problems though when opening the 2.x NIBs in IB
3.x (my NIBs contain custom objects from two different plug-ins).
It was just really annoying to always have to click "Continue".
I believe the reason for this is that the 3.x format must be saving
extra data to the NIB that may now include what Plug-Ins it depends
on. And, that such data is either not possible to add to the 2.x
format, or was overlooked.
Hmmh - I'm don't see why this would be the case:
In the past, IB used to able to find the palettes for custom classes.
I have provided plugins for these custom classes and the new IB
actually uses them - I can change the properties of my custom classes
through my IP plugin's inspector panes (after I clicked "Continue"),
so the new IB definitely _is_ able to determine the appropriate plugin.
I checked the documentation, but couldn't find a mentioning of
migrating old palettes to new plugins, so I guess I'll just have to
assume this to be a bug in IB?
Or am I still missing something in my plugin's Info.plist / source
code / NIBs that would specify this to be the sanctioned plugin for
custom classes stored in NIBs created by IB 2.x?
</jum>
_______________________________________________
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