FlowLayout class may be used by components that support layout, such as
ScrollContainer, to display items from left to right in multiple rows. It supports paging horizontally or vertically, and a number of useful options for the spacing and alignment may be modified.
Let's create a flow layout and add it to a
var layout:FlowLayout = new FlowLayout(); var container:LayoutGroup = new LayoutGroup(); container.layout = layout; this.addChild( container );
There are a number of simple properties that may be used to affect positioning and sizing of items in the layout. Let's look at some of the most common.
The padding is the space around the edges of the container. Let's set the
padding property to
layout.padding = 12;
layout.paddingTop = 10; layout.paddingRight = 15; layout.paddingBottom = 10; layout.paddingLeft = 15;
The gap is the space between items, both horizontally or vertically. Let's set the
gap property to
layout.gap = 5;
layout.horizontalGap = 4; layout.verticalGap = 6;
We can align the items in the layout using the
verticalLayout properties. Vertical alignment will only apply when the total height of the content (including padding and gap values) is less than or equal to the height of the container that uses the layout. Let's adjust the alignments so that the content will be aligned to the top left:
layout.horizontalAlign = HorizontalAlign.LEFT; layout.verticalAlign = VerticalAlign.TOP;
Since items may be smaller than the height of a row, we can align items within their rows separately from the alignment of the complete content. We'll align the items vertically in the middle of their rows:
layout.rowVerticalAlign = VerticalAlign.MIDDLE;
Virtual Flow Layout
GroupedList, the layout may be virtualized, meaning that some items in the layout will not actually exist if they are not visible. This helps to improve performance of a scrolling list because only a limited number of item renderers will be created at any given moment. If the list's data provider is very large, a virtual layout is essential, even on desktop computers that have incredible processing power compared to mobile devices.
A virtualized layout will need as estimate about how big a "virtual" item renderer should be. We should set the
typicalItem property of the list to have it determine the typical width and height of an item renderer to use as this estimated value. If we don't pass in a typical item, the first item in the data provider is used for this estimate.
true for containers that support it. We can disable virtual layouts by setting it to
false. When a layout is not virtualized, every single item renderer must be created by the component. If a list has thousands of items, this means that thousands of item renderers need to be created. This can lead to significant performance issues, especially on mobile. In general,
useVirtualLayout should rarely be disabled.
layout.useVirtualLayout = false;