There are quite a number of so-called flags for fields and controls. Flags are binary properties that can be either "on"/"active" or "off"/"inactive". They can be used to fine-tune the visual appearance and the behaviour of fields and controls.
You can see and change those flags on the Edit Fields and Controls Window, where they are represented - logically enough - by checkboxes.
General Flags
The following flags are available for almost all fields and controls, regardless of type, with only few exceptions:
Visible in card view?: With this flag set, a field or control is visible in the card view. With the flag cleared it is not visible, and there is no way to see or change its value interactively. (This flag does not extend to scripts, which can change values of such fields despite this flag set.) For new fields and controls this flags defaults to "on".
Invisible fields are more useful than one might think. They can act as a kind of persistent variables for scripts (that you don't need to see) or hold constants that cannot yet be written directly in script code because of implementation limitations, e.g. fixed dates. If you work with card lists and selections, it is also often convenient to simply hide the field containing the selecting value.
Disabled, to be skipped?: With this flag set, a field is visible, but it is disabled, which means that you cannot "visit" it, i.e. make it active and position the cursor into it if it is a text field.
A disabled field is displayed differently from a open field; it is sort of "greyed out".
Do not confuse this flag with the Read only, no modification of value?" flag, described here. It's only a side effect of the flag here that you cannot change a disabled field because it can't get the focus - the flag is about the disabling.
The flag does not influence the behaviour of scripts.
Arrange from bottom edge of card?: As explained in chapter Field and Control Placement, MoStacks can place things on a card starting from the top edge on downwards as well as starting from the bottom edge on upwards.
This flags tells to which of those two groups the field or control belongs: With the flag cleared (the default) it is in the "downwards" group, with the flag set in the "upwards" group.
The flag probably makes the most sense to set for buttons that you can place at the bottom of cards this way, if you have a stack with several backgrounds and different number of fields, and want to have the buttons in the same place on all cards, regardless of background.
Automatically maximize visible height?: With this flag set, MoStacks resizes the field to its maximum visible height, i.e. it enlarges its height until its lower edge reaches down to the field or control immediately following it, leaving only the little standard gap in between, or all the way down to the bottom edge of the card, if it is the last field.
If there are fields or controls after the one with this flag set, the flag has only an effect if those other objects have the Arrange from bottom edge of Card? flag set, otherwise there will be no free room to expand and enlarge into.
The flag is probably most useful for list fields, where one usually wants to see as much list entry as the card height allows, and for wiki fields, where one likewise wants to see as much of the text as possible.
It is better to use this flag than working out by trial-and-error for how many lines there will be room and then using that number of lines as a fixed height.
This flag is not available for Integer, Real, Boolean, Date and Time fields, because fields of those types make no sense with more than one line.
Flags for Textual Fields
On the Textual tab there are a number of flags that are mostly applicable to field types that are textual: Their values can be displayed as simple text. Those are also the field types that make sense as column in field lists.
(The correspondence is not complete, however, and you could also say "flags for fields and controls other than those of type List and Command".)
Wiki text?: With this flag set a Text field (preferably one with more than 1 line, but not necessarily so) becomes a wiki text field, with a range of interesting formatting possibilites like links to other cards, as explained in chapter Wiki.
Combo text?: With this flag set a Text field becomes the text field portion of a combo box, as explained in chapter Combo Boxes. If you set this flag while defining a new field, MoStacks will automatically create a second field for you, the List field that accompanies the text field and hold the list of the values.
Please note that MoStacks still can get confused easily if you try to set or reset this flag as a modification of an existing control. It's really a good idea to set it right away when creating the control.
Visible in card list as a column?: With this flag set the field values are displayed in an own column in the card list view. With this flag not set the values are not visible as part of the card list. This flag can be seen as the sister of the Visible in card view? flag (described here).
You can specify the title of the column for the field in the list header on the text field next to check box for this flag.
The flags is not available for fields and controls whose values have no proper textual representation, i.e. List and Command. If you set the flag for a wiki text field, the wiki formatting characters like [[ and ** will be visible which can make the card list look somewhat ugly.
Note that you can only say whether the field does or does not get a column in the card list, but there is no way yet to influence the order of the columns in that list: The field order will decide the order of the columns as well.
Read only, no modification of value?: With this flag set you cannot but is disabled so that you cannot change its value interactively. (This flag does not extend to scripts, which can change values of such fields despite this flag set. In fact, currently there is no way at all to block a field to changes by scripts.)
Flags for List Fields
You find info about lists in MoStacks in the chapter Lists.
List for a combo box?: With this flag set the control will not be visible as a separate control, but serve as the list part for a combo box. The flag is the counterpart of the Combo text? flag. The combo box next to the checkbox serves to specify the text field.
With this flag set, a lot of parameters like height or width of the list field are irrelevant, and the list of values itself (either a card list or a list given as default value) plays the central role.
Read more about combo boxes in the chapter Combo Boxes.
Card list?: With this flag set the control will be a card list as configured by a number of additional parameters like background of the cards to list. Card lists are a very powerful and versatile, but sometimes a little hard-to-configure feature of MoStacks. Details are explained in the chapter Card Lists.
Flags for Command Controls
You find info about the somewhat special control type "Command" in the chapter Commands.
Show in menu?: With this flag set the command will get an entry in the special Cmds menu of the Card View, so you can use UIQ's menu system to issue the command. The label of the control will become the function name shown in the menu.
Show as button in card view?: With this flag set the command will get a button that is placed alongside other fields and controls in the Card View, so that you can tap the button to issue the command. The button will carry the label of the control as button text.
Standard command?: With this flag set the command becomes the standard command that you configure with the help of the combo box Command next to the checkbox. Using standard commands is much easier than writing scripts and assign them to commands, but what they can do is rather limited. You find a list of the standard commands in the chapter Commands.
Show as picture button?: For each standard command there is an picture/icon defined by MoStacks. With this flag set a command configured as a standard command and shown as a button displays that icon instead of a button text.