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".
It'll also show the entire hierarchy, even the invisible pieces, which was invaluable for tracking down the views that had collapsed to size (0,0) due to some unfortunate pre-autolayout legacy behavior. ________________________________________ From: xcode-users-bounces+lrucker=vmware....@lists.apple.com [xcode-users-bounces+lrucker=vmware....@lists.apple.com] on behalf of Bill Cheeseman [wjcheese...@gmail.com] Sent: Wednesday, March 16, 2016 7:12 AM To: xcode-users Subject: Re: Question about debugging OS X Auto Layout On Mar 16, 2016, at 5:35 AM, Bill Cheeseman <wjcheese...@gmail.com<mailto:wjcheese...@gmail.com>> wrote: As to my question, I thought on it overnight and figured out that the only affected constraints would be those from any view in the affected scenes to their superview in the view hierarchy. That will substantially simplify the repair job. I'll try that later today and hope I'm right. On Mar 15, 2016, at 3:46 PM, Lee Ann Rucker <lruc...@vmware.com<mailto:lruc...@vmware.com>> wrote: Start by giving all your views identifiers, that'll make them easier to track down; the error message will use the name and you can search for it in IB. Unfortunately, after adding identifiers to all views I can see in my Interface Builder storyboard, the same error message is logged about an invalid constraint, and the error message uses none of the identifiers. This suggests to me that the storyboard file became corrupted when I deleted and reinstalled some segues and renamed some view controllers. Is it possible for a storyboard file to contain "ghost" constraints that can't be seen in Interface Builder but prevent the application from running? Is there any way to debug this or to remove the errors? This is a large, complex storyboard, and I sure don't want to have to rebuild it from scratch. 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<mailto: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
