Re: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?
Re: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?
- Subject: Re: Nib Corruption ("Inconsistencies"): Can This Nib Be Saved?
- From: Vince DeMarco <email@hidden>
- Date: Sun, 26 Jan 2003 16:52:00 -0800
On Sunday, January 26, 2003, at 01: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 :-)!
THere is a bug in NSTableView, that it removes all of the columns when
the autosavename is set. For now the solution is to not use the
autosave name in NSTableView's
please file a bug..
vince
_______________________________________________
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.