The simplest language to explain is that both setframe and setbounds are loaded into the parent view for the handle view, but the parameter coordinate system is set differently, and the setframe is the position and size of the view in the parent view coordinates. SetBounds is the position and size of the view in the local coordinate system.
Here's the stolen information:
Look at sketch and you'll see.
Frame: The position and size of the view in the parent view coordinate system. (reference point is, Father's coordinate system)
Bounds: The position and size of the view in the local coordinate system. (The reference point is that the local coordinate system is equivalent to VIEWB's own coordinate system, starting at 0, 0 points)
Center: The position and size of the view's central point in the parent view coordinate system. (Reference electricity is, father's coordinate system)
Personally, I think, bounds a little puzzled, a little inattentive, think more, will go around. Each view has a local coordinate system. This coordinate system function is more important, such as the touch of the callback function in the Uitouch inside the > Coordinate values are reference to the local coordinate system coordinates. Of course bounds this attribute is also referred to this local coordinate system. In fact, the key of the local coordinate system is to know where its origin (0,0) is located (this position is relative to the upper view of the local coordinate system, of course, the top layer of view is the window its local coordinate system origin is the upper left corner of the screen). The local coordinate system's origin location can be modified by modifying the view's Bounds property.
iOS frame and bounds differences