On Mar 16, 2016, at 11:22 AM, Ken Thomases < email@hidden> wrote:
On Mar 16, 2016, at 9:12 AM, Bill Cheeseman <email@hidden> wrote:
"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>"
At the very least, you should concentrate on tab views, constraints involving their leading edges, with priority 749. Do you have many tab views in your storyboard?
My storyboard has 3 tab views, 2 of them with 3 tab view items each, and 1 of them with 16 tabless tab view items used to switch between sets of controls depending on the current selection in a table. It is a manageable job to examine all of them. I am using the new NSTabViewController for all 3 tab views, and until this problem arose they were all working as expected.
I found advice online to open the storyboard "as source" in Xcode in order to examine it as an XML file. Very nice. Unfortuately, searching on "749" tells me that NOTHING in the storyboard file has priority 749. How can that be, when the Xcode runtime error message says that there is?
I have now eyeballed all the tab views and their constraints in XML format, and I have used search terms like "tab", "leading" and "priority" to search for out-of-place items. I can't find anything that looks suspicious. So now I'm really puzzled, and I don't know what to do next. |