I haven't looked at your NIB, but I've seen something of what's described with errant choices of diff tools and source code merging, usually when a user just accepts a merge without eyeballing it. If you've got a history of your revisions, you should find where things changed badly. Also, if you've got a built app that works, I remember being able to add some extra things on older NIBs to make them openable in Interface Builder, but that was a really long time ago.
When editing the text of a NIB, you have to be really careful with internal identifiers, which are essentially freeze-dried pointers within the NIB, and this may be why your forensic work is failing. When I've had to resort to this (nowadays in cases of auto layout mainly) I let Apple know that this is the only way I could do this or that. Basically, try to find your oldest working version and go forward with that. If you can compare a working vs immediately non-working, that's even better. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ > On Feb 13, 2017, at 8:58 AM, Andreas Falkenhahn <andr...@falkenhahn.com> > wrote: > >> On 13.02.2017 at 17:33 じょいすじょん wrote: >> >> Yeah, my first suggestion didn't work, but points out the problem overall in >> you nib. >> Looks like somebody did try to edit the xml before and munged it. > > I certainly did not mess with the XML! Xcode must have messed this up when > converting > the nib file from the old Xcode PowerPC project format to the new one. > >> You also have nested menu duplicates inside your menus in the nib file >> itself! > >> MainMenu >> Hollywood >> Menu >> About Hollywood >> Separator >> MainMenu (duplicated here as sub menu...) >> Preferences >> ... (and on) > > >> Delete that other MainMenu inside and it seems to work thus far. > > I've removed the complete duplicate MainMenu tree (the one after the separator > item, see above) from designable.nib using a text editor. However, it still > doesn't work. Same behaviour as before. > > <rant> > > This annoying issue is just another reason why I prefer doing things in code. > This has already cost me hours over hours and it's still not solved. Even > worse, there's a profound feeling of helplessness in the air. And re-creating > everything from scratch is not an option! I certainly did not mess with the > XML. Xcode must have messed this up when converting the project from the > old format to the new one. All such things wouldn't be possible with code. > Code could be cleanly adapted to new designs while nobody can tell what black > magic is going on inside those arcane nib files. It's quite depressing. $0.02 > > </rant> > > -- > Best regards, > Andreas Falkenhahn mailto:andr...@falkenhahn.com > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
