> On Mar 17, 2016, at 4:55 AM, Bill Cheeseman <wjcheese...@gmail.com> wrote: > > I tried that, but it won't work because the storyboard won't load. That's a > little discourging: Sorry, bud, you can't debug it because it has a bug in it. > >> On Mar 16, 2016, at 7:59 PM, Lee Ann Rucker <lruc...@vmware.com >> <mailto:lruc...@vmware.com>> wrote: >> >> Next step I'd do is use the visual debugger; it's not as easy but you can >> find the view based on the address, or worst case just do something like "po >> 0x600000120c80".
I didn't fully understand what you were suggesting. The storyboard does in fact load, but it only shows the empty window with its title bar because, as the error message states, it could not set the NSContentViewController of the NSWindow. But you're right, the application is still running in the debugger and I can use debugger commands like "po 0x600000120c80". Unfortunately, that just echos back something like "<NSTabView: 0x600000120c80>", which tells me nothing. So far, I haven't figured out any useful commands to give the debugger. I did make this little tiny bit of progress: It dawned on me that I could copy the storyboard file in XML format, paste it into a text file in TextWrangler or the like, then save that text file as Main.storyboard in my Xcode project in place of the original storyboard file. I did that, and it generated exactly the same error message. This proves to me that the storyboard file did not in fact get corrupted by my renaming of a couple of classes, as I originally suspected. It is in fact a valid XML file. Instead, I now surmise that my storyboard file as written contains a logical error that causes this failure at run time. It is clear to me that at run time it creates at least one new automatic constraint (that mysterious constraint having priority 749). The error message is useless because it does not give me a clue about how to find the combination of features in my storyboard file that apparently generates a bad automatic constraint. I have spent a day now studying my constraints in those storyboard scenes that are closely related to tab views, as referenced in the error message, but I haven't yet found any place where I use an "illegal" reference to "something from outside the subtree of the view." My next effort will be to install Xcode 7.3 beta 5, on the off chance that OS X storyboards and auto layout constraints have been improved. Here's the error message again: "2016-03-15 14:28:14.801 UI Browser[93092:22589120] Failed to set (contentViewController) user defined inspected property on (NSWindow): Unable to install constraint on view. Does the constraint reference something from outside the subtree of the view? That's illegal. constraint:<NSLayoutConstraint:0x608000085910 'NSTabViewController-TabViewLeading' NSTabView:0x100d18d50.leading == NSView:0x600000120c80.leading priority:749> view:<NSView: 0x600000120c80>" -- Bill Cheeseman - wjcheese...@comcast.net
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
