For a Xamarin Forms app, there are several layout containers to choose from. Most UIs should be achievable with a StackLayout or a GridLayout. There are a few exceptions when those two won’t solve the problem. This post is an example of Xamarin Forms relative layout.
The Problem: Why a RelativeLayout
I had to show an triangle in the corner of the screen. See the image below. A StackLayout is very difficult to get items to overlap, a negative margin can be used, but only for a known distance (won’t always work for screens with different sizes). Items can be overlapped with a GridLayout if they are placed in the same cell. This renders the items over the entire cell, and my requirement was only part of the cell, the triangle. Using XAML only, this is not possible, and could only be done in code with a translation.
What is a View
A view, the ‘things’ that we’re trying to layout on the screen and requires a few key pieces of information, called attributes.
- An origin to start drawing the item from. This is an X and Y value, with (0,0) at the top left-hand corner (of the device or container it’s being drawn in)
- A width
- A height
Setting the attributes of a child
A RelativeLayout allows you to specify the X, Y, Width and Height of a child. The values that are set can be pulled from any other child or parent. They do not, need to be the same attribute (X, Y, Width, Height). To set the attributes of the child is as follows:
1: 2: 3: 4:
The simplest value to apply to each of these is the same as the parent. Setting all four values to be the same as the parent would make the view fill the space the parent is given. This is as follows
1: 2: 3: 4:
First, the value must be declared as ConstraintExpression. The type of the relationship is then declared, in this case, RelativeToParent, we’ll look at another one is just a moment. The last line also shows two extra parameters that can be used (and are generally needed to do anything useful with RelativeLayout). The constant attribute simply adds the value to the property (like an offset). ie for HeightConstraint if constant=10 then the height would be the property + 10. The value can be negative. A factor is simply a multiplier to the Property attribute. eg.
If the width of the parent is 480 and the factor is 0.5 then the with of the item will be 240 meaning the view will be half the width of the parent.
The Relative part of a RelativeLayout
Each of the four attributes can be set from any attribute of another view with the relative layout. They can also be expressed relative to another view. The other view needs to be named using
x:Name="itemName". To get values out of the view use
Type=RelativeToView and then specify the name of the view with the Element tag
Element=itemName finally to get the value out
Property=Height or any other attribute name that is required. An example is below:
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11:
The first BoxView will fill the entire screen. The second BoxView will fill the bottom half of the screen. The with is equal to the width of itemName, which is set to the width of the screen.
How I did the Triangle
As already shown in the image above, I needed to show a triangle in the top left corner of a cell (the cell is part of a ListView), and I also wanted it to scale for screen sizes (the test was to rotate to landscape and still have everything layout correctly). This was achieved by nesting everything in a relative layout. The content was placed in a StackLayout. A BoxView was then used for the triangle. It was set relative to the origin, a fixed width and a negative constant so that it is always placed correctly. Add some rotation and it’s now a triangle. Because the width is always fixed size then the constant value can be known to ensure it will always be placed correctly. Here’s the XAML to make it clear.
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13:
What it can’t do
For those who have used RelativeLayout in android, Xamarin Forms’ RelativeLayout is not as expressive in XAML. For a page to be effective, it’s best to avoid fixed sizing, or it won’t scale well on all those Android devices (and the growing number of devices for apple too). Halfway through this post I tried to create a great example using a RelativeLayout and xaml only to find that it can’t be done, constants would have been required, so a GridLayout would have been better.
RelativeLayout can’t be a StackLayout. In order to place one view below the other, you would need to set the Y value of the bottom view equal to the Y value of the top view + the height. This calculation can’t be done in XAML. As a result, it’s difficult to lay out a view that will fit all screen sizes. Using the Constant attribute doesn’t work well across screen sizes.
It can’t be a GridLayout as well for the same reason as the StackLayout, it’s not possible in XAML to add values together.
RelativeLayout is great for adding a few styles, but for most of your views stick to GridLayout and StackLayouts.