You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I refer to myView indirectly using mySubView.superview. This is because it often eases refactoring, for instance if I want to introduce a container view between myView and mySubView.
I wonder if it would make sense to introduce a make.superview? This way, the constraints related to the actual view would be easier to recognize.
Also, I try to use mas_makeConstraints: as often as I can, since in my mind, constraints are almost always immutable, except when animating.
What are your comments to the above points? Are they patterns or anti-patterns? :-)
The text was updated successfully, but these errors were encountered:
I often use a pattern as the following:
So I refer to myView indirectly using mySubView.superview. This is because it often eases refactoring, for instance if I want to introduce a container view between myView and mySubView.
I wonder if it would make sense to introduce a make.superview? This way, the constraints related to the actual view would be easier to recognize.
Also, I try to use mas_makeConstraints: as often as I can, since in my mind, constraints are almost always immutable, except when animating.
What are your comments to the above points? Are they patterns or anti-patterns? :-)
The text was updated successfully, but these errors were encountered: