On 14.02.2017 at 23:15 Graham Cox wrote: > It’s usually easier to float downstream.
+1 for nice metaphor. On the good news side: I've fixed it now. The trick was to first fix the spurious menu trees directly in the XML, then to delete keyedobjects.nib, then to make a dummy change directly in Interface Builder to force it to re-compile keyedobjects.nib and then it finally worked. That was quite a tough one but I still feel more satisfied now than I'd have been if I had re-created the whole shebang from scratch, even though that'd probably have been faster. > Sure, it could be. Bugs happen. XCode bugs happen a lot. That definitely seems so because I definitely didn't mess with the XML but still the whole menu tree was listed as a submenu of a separator item and when examining the XML generated by my PPC Macintosh version of Xcode the menu tree definition is correct in that file. So it must have been introduced during transitioning to the latest Xcode (Or I did something really stupid without realizing it but I can't imagine that it's even possible in Xcode to duplicate the whole menu tree and insert it as a submenu of a separator item. That's just utter non-sense and that's why it didn't appear in Xcode either, just in the XML.) Anyway, issue fixed. Thanks to all who helped! -- 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
