Re: NIB file problems (possibly corrupt)
Re: NIB file problems (possibly corrupt)
- Subject: Re: NIB file problems (possibly corrupt)
- From: Ian Joyner <email@hidden>
- Date: Fri, 9 Mar 2007 10:49:42 +1100
I seem to have fixed this. The step before I got rid of the hang was
to open the offending Nib, not from Xcode, but from Finder. Of course
I got a lot of things not connected or found, but IB was not hanging
up when I clicked on the display groups. So I saved it, and back in
Xcode it now works. Mind you I am still getting the error messages,
and the five verification errors reported in console, which I'd like
to get rid of.
Hmmm, this methinks is hacking, not programming, although Bertrand
Meyer once or more times said "Hacking's good" – I think he meant
more the experimental hacking, where your software development
practices are so good, you're not afraid to try things out.
Ian
On 07/03/2007, at 4:15 PM, Ian Joyner wrote:
Although, I'm using IB for WebObjects, there was no help in the WO
group for this problem since very few do Java Client development.
It seems like a general problem with IB, so maybe you nice Cocoa
people might be able to help unscrew IB, thanks. Even if you can't
answer the particular problem, are there any general techniques for
getting a NIB back into a usable state?
When I open a NIB file in IB (latest version 2.5.4 and WO 5.3.3), I
get a dialog:
"Interface Conversion
The interface file Main_interface_controller.nib has been updated
to a newer version. After saving it you will not be able to open it
on other platforms any more and you will not be able to use it with
older versions of WebObjects/EOF."
So I press OK and get another dialog:
"Open Interface
5 inconsistencies in the document were found and repaired. Please
save the document"
and the following appears in Console:
2007-03-06 16:14:58.036 Interface Builder[23973] **** verification
error ****: destination <EODetailDataSource: 0xc80c2f0> on
connector <NSNibOutletConnector: 0xc875660> is not in objectTable.
2007-03-06 16:14:58.036 Interface Builder[23973] **** verification
error ****: destination <EODetailDataSource: 0xc80c2f0> on
connector <NSNibOutletConnector: 0xc874500> is not in objectTable.
2007-03-06 16:14:58.036 Interface Builder[23973] **** verification
error ****: destination <EODetailDataSource: 0xc80c2f0> on
connector <NSNibOutletConnector: 0xc837e40> is not in objectTable.
2007-03-06 16:14:58.036 Interface Builder[23973] **** verification
error ****: destination <EODetailDataSource: 0xc80c2f0> on
connector <NSNibOutletConnector: 0xc8222f0> is not in objectTable.
2007-03-06 16:14:58.036 Interface Builder[23973] **** verification
error ****: destination <EODetailDataSource: 0xc80c2f0> on
connector <NSNibOutletConnector: 0xc8bafa0> is not in objectTable.
So I save the document, but the same happens next time I open the NIB.
What is worse though, if I select any display group (or try to do
anything with them like display connections to a display group from
a search text field, IB goes into a loop and writes the following
out to the Console (although I'm feeling pretty inconsolable at
this point):
2007-03-06 16:17:22.949 Interface Builder[23973] ObjCJava: no java
object for 0x59531a0<JDBCAdaptor>
2007-03-06 16:17:22.949 Interface Builder[23973] ObjCJava: can't
forward method description
2007-03-06 16:17:22.949 Interface Builder[23973] ObjCJava: no java
object for <JDBCAdaptor: 0x59531a0>
2007-03-06 16:17:22.949 Interface Builder[23973] ObjCJava: can't
forward method initWithName:
2007-03-06 16:17:22.951 Interface Builder[23973] Exception raised
during posting of notification. Ignored. exception:
initWithPropertyList:owner:: cannot find entity named Address for
destination of relationship addresses in entity Group.
2007-03-06 16:17:22.958 Interface Builder[23973] *** -[EOAttribute
isEqualToString:]: selector not recognized [self = 0x595c760]
2007-03-06 16:17:22.958 Interface Builder[23973] *** -[EOAttribute
isEqualToString:]: selector not recognized [self = 0x595c760]
The application runs OK, except the search text field does not work
anymore (may or may not be related).
So, is there a way of repairing the NIB, or any other way around this?
Thanks
Ian Joyner
Sportstec
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
40sportstec.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden