Card View
- 2 minutes to read
A Card View displays rows using a card display metaphor – each row is shown in a separate block within the View (a card). When in its regular layout, a row within a card is drawn vertically, so more space is available for detail data.
The ultimate purpose of a Card View is to provide you with more display “real-estate” than is possible when using a Table View or a Banded Table View. The TcxGridCardView and TcxGridDBCardView classes implement logic for the unbound and data-aware Card Views.
Similar to Table and Banded Table Views, a Card View offers different ways of data manipulation, such as data filtering or the logical grouping of rows.
For this View type, a row is represented by the TcxGridCardViewRow class. It offers a rich set of properties, most of which are common to other ExpressQuantumGrid Views. Card Views also provide additional properties such as row type specification, the row’s appearance, and its position in a card (see the row’s Kind, Styles and Position properties).
A collection of rows in a Card View is accessible through the View’s Rows property.
Laying out rows in a card
For extended card layout, ExpressQuantumGrid has a layer mechanism. Layering is a process of dividing a card into spaces – flat layers. Each layer can contain a different set of rows. Rows can be visually laid out in layers (both vertically or horizontally). They flow from top to bottom, if a card is layered vertically (the View’s RowLayout property is set to rlVertical).
…And are arranged from left to right if a card is layered horizontally (the View’s RowLayout property is set to rlHorizontal).
To break a card into layers, set the Position.BeginsLayer property of rows that will start a layer, to True.