I would like to know how to use these properties in the right manner.
As I understand, frame
can be used from the container of the view I am creating.
It sets the view position relative to the container view. It also sets the size of that view.
Also center
can be used from the container of the view I'm creating. This property changes the position of the view relative to its container.
Finally, bounds
is relative to the view itself. It changes the drawable area for the view.
Can you give more info about the relationship between frame
and bounds
? What about the clipsToBounds
and masksToBounds
properties?
I think if you think it from the point of
CALayer
, everything is more clear.Frame is not really a distinct property of the view or layer at all, it is a virtual property, computed from the bounds, position(
UIView
's center), and transform.So basically how the layer/view layouts is really decided by these three property(and anchorPoint), and either of these three property won't change any other property, like changing transform doesn't change bounds.
This question already has a good answer, but I want to supplement it with some more pictures. My full answer is here.
To help me remember frame, I think of a picture frame on a wall. Just like a picture can be moved anywhere on the wall, the coordinate system of a view's frame is the superview. (wall=superview, frame=view)
To help me remember bounds, I think of the bounds of a basketball court. The basketball is somewhere within the court just like the coordinate system of the view's bounds is within the view itself. (court=view, basketball/players=content inside the view)
Like the frame, view.center is also in the coordinates of the superview.
Frame vs Bounds - Example 1
The yellow rectangle represents the view's frame. The green rectangle represents the view's bounds. The red dot in both images represents the origin of the frame or bounds within their coordinate systems.
Example 2
Example 3
Example 4
This is the same as example 2, except this time the whole content of the view is shown as it would look like if it weren't clipped to the bounds of the view.
Example 5
Again, see here for my answer with more details.
Since the question I asked has been seen many times I will provide a detailed answer of it. Feel free to modify it if you want to add more correct content.
First a recap on the question: frame, bounds and center and theirs relationships.
Frame A view's
frame
(CGRect
) is the position of its rectangle in thesuperview
's coordinate system. By default it starts at the top left.Bounds A view's
bounds
(CGRect
) expresses a view rectangle in its own coordinate system.Center A
center
is aCGPoint
expressed in terms of thesuperview
's coordinate system and it determines the position of the exact center point of the view.Taken from UIView + position these are the relationships (they don't work in code since they are informal equations) among the previous properties:
frame.origin = center - (bounds.size / 2.0)
center = frame.origin + (bounds.size / 2.0)
frame.size = bounds.size
NOTE: These relationships do not apply if views are rotated. For further info, I will suggest you take a look at the following image taken from The Kitchen Drawer based on Stanford CS193p course. Credits goes to @Rhubarb.
Using the
frame
allows you to reposition and/or resize a view within itssuperview
. Usually can be used from asuperview
, for example, when you create a specific subview. For example:When you need the coordinates to drawing inside a
view
you usually refer tobounds
. A typical example could be to draw within aview
a subview as an inset of the first. Drawing the subview requires to know thebounds
of the superview. For example:Different behaviours happen when you change the
bounds
of a view. For example, if you change thebounds
size
, theframe
changes (and vice versa). The change happens around thecenter
of the view. Use the code below and see what happens:Furthermore, if you change
bounds
origin
you change theorigin
of its internal coordinate system. By default theorigin
is at(0.0, 0.0)
(top left corner). For example, if you change theorigin
forview1
you can see (comment the previous code if you want) that now the top left corner forview2
touches theview1
one. The motivation is quite simple. You say toview1
that its top left corner now is at the position(20.0, 20.0)
but sinceview2
'sframe
origin
starts from(20.0, 20.0)
, they will coincide.The
origin
represents theview
's position within itssuperview
but describes the position of thebounds
center.Finally,
bounds
andorigin
are not related concepts. Both allow to derive theframe
of a view (See previous equations).View1's case study
Here is what happens when using the following snippet.
The relative image.
This instead what happens if I change
[self view]
bounds like the following.The relative image.
Here you say to
[self view]
that its top left corner now is at the position (30.0, 20.0) but sinceview1
's frame origin starts from (30.0, 20.0), they will coincide.Additional references (to update with other references if you want)
About
clipsToBounds
(source Apple doc)In other words, if a view's
frame
is(0, 0, 100, 100)
and its subview is(90, 90, 30, 30)
, you will see only a part of that subview. The latter won't exceed the bounds of the parent view.masksToBounds
is equivalent toclipsToBounds
. Instead to aUIView
, this property is applied to aCALayer
. Under the hood,clipsToBounds
callsmasksToBounds
. For further references take a look to How is the relation between UIView's clipsToBounds and CALayer's masksToBounds?.There are very good answers with detailed explanation to this post. I just would like to refer that there is another explanation with visual representation for the meaning of Frame, Bounds, Center, Transform, Bounds Origin in WWDC 2011 video Understanding UIKit Rendering starting from @4:22 till 20:10
I found this image most helpful for understanding frame, bounds, etc.
Also please note that
frame.size != bounds.size
when the image is rotated.After reading the above answers, here adding my interpretations.
Suppose browsing online, web browser is your
frame
which decides where and how big to show webpage. Scroller of browser is yourbounds.origin
that decides which part of webpage will be shown.bounds.origin
is hard to understand. The best way to learn is creating Single View Application, trying modify these parameters and see how subviews change.