When removing the subview, all the constraints that relate to that subview will be lost. If you need to add the subview again later, then you must add constraints to that subview again.
Typically, I create the constraints in my custom subview. For example:
-(void)updateConstraints
{
if (!_myLayoutConstraints)
{
NSMutableArray *constraints = [NSMutableArray array];
// Create all your constraints here
[constraints addWhateverConstraints];
// Save the constraints in an ivar. So that if updateConstraints is called again,
// we don't try to add them again. That would cause an exception.
_myLayoutConstraints = [NSArray arrayWithArray:constraints];
// Add the constraints to myself, the custom subview
[self addConstraints:_myLayoutConstraints];
}
[super updateConstraints];
}
updateConstraints
will be called automatically by the Autolayout runtime. The code above goes in your custom subclass of UIView
.
You're right that in working with Autolayout, you don't want to touch frame sizes. Instead, just update the constraints in updateConstraints
. Or, better still, set up the constraints so you don't have to.
See my answer on that topic:
Autolayout UIImageView with programatic re-size not following constraints
You don't need to set the initial frame. If you do use initWithFrame
, just set it to CGRectZero
. Your constraints will - in fact must - detail either how big something should be, or other relationships that mean the runtime can deduce the size.
For example, if your visual format is: @"|-[myView]-|"
, that's everything you need for the horizontal dimension. Autolayout will know to size myView
to be up to the bounds of the parent superview
denoted by |
. It's pretty cool.