9,334
edits
View: Difference between revisions
Jump to navigation
Jump to search
→Properties pane
| Line 66: | Line 66: | ||
In both cases, you must select from a list of fields. Click '''OK''' to confirm your selection. | In both cases, you must select from a list of fields. Click '''OK''' to confirm your selection. | ||
== Properties pane == | === Properties pane === | ||
The following properties can be configured on '''View''' level: | The following properties can be configured on '''View''' level: | ||
* Columns: On wider screens, you can display multiple list items in one line. This can be particularly useful for custom rows; for example when you want to create your view as a gallery of images. The value of Columns is the maximum number of records to display in one line; however, fewer records will be displayed on narrow screens. | * Columns: On wider screens, you can display multiple list items in one line. This can be particularly useful for custom rows; for example when you want to create your view as a gallery of images. The value of Columns is the maximum number of records to display in one line; however, fewer records will be displayed on narrow screens. | ||
| Line 96: | Line 96: | ||
* Anchor – Anchors fix the boundary position of the field to the side the anchor is pointing to. | * Anchor – Anchors fix the boundary position of the field to the side the anchor is pointing to. | ||
=== Binding === | ==== Binding ==== | ||
Binding determines which entity field is displayed in a cell. It is actually a combination of two properties: type and value. | Binding determines which entity field is displayed in a cell. It is actually a combination of two properties: type and value. | ||
| Line 104: | Line 104: | ||
* Raw Value – this makes sense for example for option sets, if you want to display the numeric representation of an option, rather than its label. This is useful, if you don’t want to display text, but different view images, or map pins based on different value of the option set. It is because images cannot have space in their names | * Raw Value – this makes sense for example for option sets, if you want to display the numeric representation of an option, rather than its label. This is useful, if you don’t want to display text, but different view images, or map pins based on different value of the option set. It is because images cannot have space in their names | ||
* Constant – this binding type allows you to enter static text. The exact text is displayed in the app, instead of the entity field data. This way you can add labels to views, for example to describe fields that only show numeric values. | * Constant – this binding type allows you to enter static text. The exact text is displayed in the app, instead of the entity field data. This way you can add labels to views, for example to describe fields that only show numeric values. | ||
==== Anchors ==== | |||
Each field has four available anchors. Click an anchor to toggle it on and off. Active anchors fix the boundary position of the field to the side the anchor is pointing to. In the case of the picture below, the City field binds to the left border of the view item and to the bottom border of the Name field. When the anchors are set correctly, the view will not be scrambled when users rotate the screen, e.g., from portrait to landscape. | |||
[[File:Anchor.png|600px]] | |||
For more information about anchors, see [https://blog.resco.net/2018/10/17/advanced-tip-managing-cell-anchors-in-views/ Advanced tip: Managing cell anchors in views]. {{Badge|Blog}} | |||
== Edit styles == | == Edit styles == | ||