• 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: IB3: DO NOT USE for Carbon!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IB3: DO NOT USE for Carbon!


  • Subject: Re: IB3: DO NOT USE for Carbon!
  • From: Jonathan Hess <email@hidden>
  • Date: Fri, 8 Feb 2008 14:27:21 -0800


On Feb 8, 2008, at 5:35 AM, Norbert M. Doerner wrote:

Hi!

I haven't had the chance to investigate this thoroughly yet, but a quick investigation reveals that saving in Interface Builder 3.0 NIB format should work around this issue.

But that won't work for apps running in 10.4, right?

Hey Norbert -

IB 3.0 supports three file formats. The 2.x file format is the same file format that's been in use in Interface Builder previously. It can be edited by IB 2.0, and is deployable on earlier versions of Mac OS X. The NIB 3.x file format supports all the new features, is also deployable on earlier versions of Mac OS X, but can only be edited with IB 3.0. IB 3.0 also supports a textual, human-readable format called the "xib" format. This format is equivalent to the 3.x format, but it's more SCM-friendly. It is compiled down to a 3.x file at build time.

For editing and building your project on Leopard only, we recommend the xib format, since it provides the best development time experience. If you need to build your project on Tiger, but edit your nibs on Leopard only, then you can use the 3.x format. Finally, if you wish to be able to continue to edit your nib files on Tiger, you can stick to the 2.x format. In all these cases, the files can be deployed on 10.0+, but some features supported by IB 3.0 may not work on the earlier systems. IB has facilities to warn you in those cases.

Good Luck -
Jon Hess



Thank you very much!!!


Jon Hess

On Feb 8, 2008, at 2:55 AM, Norbert M. Doerner wrote:

Hi folks!

I have just discovered a major bug in Interface Builder 3, and I would like to make sure all Carbon developers know about it:

If IB3 loads Carbon NIBs, it destroys the CommandID of controls, if these are non-textual (if you have unchecked the '4chr' checkbox and use numerical values for the ID). If you save these NIBs, the values are all damaged.

This actually renders IB3 totally useless until fixed. I found that by coincidence, and now I have to fix several damaged NIB files, all manually, and all in IB 2.5, which actually works fine...

rdar://5731765

PS: I know that Apple wants us to get rid of Carbon quickly, but isn't that a bit drastic? ;-)) OK, just kidding...

--

Norbert M. Doerner
CEO, West-Forest-Systems
In der Trift 13
56459 Langenhahn, Germany
Fax: +49 (2663) 91 70 126
-----------------------------------------------------
** CDFinder for Macintosh ** The Search Is Over! <http://www.cdfinder.de/ >
Also available: CDWinder for Windows: <http://www.cdwinder.de>
-----------------------------------------------------

_______________________________________________ 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
References: 
 >IB3: DO NOT USE for Carbon! (From: "Norbert M. Doerner" <email@hidden>)
 >Re: IB3: DO NOT USE for Carbon! (From: Jonathan Hess <email@hidden>)

  • Prev by Date: Re: warning: argument to '&' not really an lvalue
  • Next by Date: Re: IB3 Frustration
  • Previous by thread: Re: IB3: DO NOT USE for Carbon!
  • Next by thread: gdb breakpoints for synthesized properties
  • Index(es):
    • Date
    • Thread