• 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: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?


  • Subject: Re: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?
  • From: Alex Rice <email@hidden>
  • Date: Mon, 27 Jan 2003 10:25:05 -0700

On Sunday, January 26, 2003, at 02:40 PM, Buzz Andersen wrote:

I appear to have finally encountered the dreaded Nib file corruption I've heard so much about. Whenever I open my application's MainMenu.nib, I now get a message telling me that their are "inconsistencies" in the file and that I should re-save it.

I'm not sure quite how I precipitated this problem, but I do know it has something to do with an NSTableView that is stored in the nib. Normally this NSTableView has the autosave name "songTable," and as long as it stored with that name, I get the error every time I open the nib in IB. If I remove the autosave name, there is no problem. I have even tried deleting the pre-existing NSTableView and creating a new one, but as soon as I put the autosave name back in, I have the problem again. I've also tried, just for the sake of experimentation, saving the nib using the pre-10.2 format and then re-saving it using the 10.2 format I normally use. No dice :-(.

Does anyone know any way that I can fix this problem without having to re-create my app's entire interface? Is there any way I can just get it to "forget" about songTable, and then re-create it? Any help would be hugely appreciated :-)!

Actually I think Matt G. is on the right track, but not exactly. Delete your preferences for Interface Builder; or locate the key where IB is storing the state for your NSTableView columns. I encountered this same after removing or renaming some columns from a TableView. However, InterfaceBuilder has already cached the names and states of the columns. Well those columns don't exist any more... IB panics and can't open the nib file without whacking some columns for you. Not a pleasant experience.

Easy solution:
defaults delete com.apple.InterfaceBuilder

More accurate solution:
defaults read com.apple.InterfaceBuilder | more
then look for the key with the autosave-name of your table, e.g.
"NSTableView Columns MLSlacker2OutlineView"

then do
defaults delete com.apple.InterfaceBuilder "the key name"
e.g.
defaults delete com.apple.InterfaceBuilder "NSTableView Columns MLSlacker2OutlineView"

This seems like a major bug in IB, to me, but I don't follow the ProjectBuilder mailing list. Can anyone confirm it's been reported to apple?

Alex Rice <email@hidden> | Mindlube Software | http://mindlube.com

what a waste of thumbs that are opposable
to make machines that are disposable -Ani DiFranco
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Nib Corruption ("Inconsistencies"): Can This Nib Be Saved? (From: Buzz Andersen <email@hidden>)

  • Prev by Date: Re: Making an NSMenu "small"?
  • Next by Date: copyPath and performFileOperation
  • Previous by thread: Re: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?
  • Next by thread: Making an NSMenu "small"?
  • Index(es):
    • Date
    • Thread