Today, when you add constraints to your view to compare previously added constraints, there are two layers of light red wireframe a solid line and a dashed line, whereas the previous demo added only a solid blue wireframe.
The constraint 1 added today is as follows:
Figure 1
As previously added, constraint 2 shows:
Figure 2
Later, when you add a button to the first constraint under a peer view, the Discovery button leaks part of the
=
This problem does not occur if you are constrained in the second way
=
What is this for?
The original is the margin attribute in mischief. The margin property represents the distance from the surrounding element, as opposed to the padding attribute representing the distance within the element from its own boundary. As shown in [1]:
When you add a PIN constraint, the constrain to margins option is checked by default, so that the added constraint automatically uses the default margin constraint
Therefore, when adding pin constraints, found that there is a gap, and "leaking out" part of the hope to be obscured the content, must be careful to pay attention to this problem.
Reference
[1] http://blog.163.com/email_wangyong/blog/static/126152455200972431013536/
There is a gap in the IOS pin constraint issue