• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Interface Builder can't identify plugins when opening old NIBs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interface Builder can't identify plugins when opening old NIBs


  • Subject: Re: Interface Builder can't identify plugins when opening old NIBs
  • From: Ricky Sharp <email@hidden>
  • Date: Sat, 10 Nov 2007 06:27:19 -0600


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. 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.

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com

_______________________________________________
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


  • Follow-Ups:
    • Re: Interface Builder can't identify plugins when opening old NIBs
      • From: Jens Miltner <email@hidden>
References: 
 >Interface Builder can't identify plugins when opening old NIBs (From: Jens Miltner <email@hidden>)

  • Prev by Date: "file is not of required architecture" error on most sample code builds on xcode 3
  • Next by Date: Re: gdb cvs
  • Previous by thread: Interface Builder can't identify plugins when opening old NIBs
  • Next by thread: Re: Interface Builder can't identify plugins when opening old NIBs
  • Index(es):
    • Date
    • Thread