AreaList Pro version 10 documentation

• Default for LTR system is 1.
• Default for RTL system is 7.
• Checkbox, radio buttons and “draw integers as pictures” are always handled directly, not in the 10.0 entry widget.
• Not using the 10.0 entry widget for styled text (i.e. bit 0 false) means the 10.1 native editor is used and the user will edit
“<SPAN …>text</SPAN>”, not styled text.
• Using the 10.0 entry widget means you can use ALP_Column_EntryFormat, but you can’t have keyboard shortcuts executed for your form during editing.

* ALP_Area_EntryFirstClickMode = 0, cell value does not matter: that click is interpreted by the widget → no selection, caret is somewhere in the text.
* ALP_Area_EntryFirstClickMode = 1, value is “not empty” (e.g. 123.45) - identical to ALP_Area_EntryClick = 0.
* ALP_Area_EntryFirstClickMode = 1, value is “empty” (e.g. 0.00) - that zero is selected, caret is at the end.
* ALP_Area_EntryFirstClickMode = 2, value is “not empty” (e.g. 123.45) - that value is selected, caret is at the end.
* ALP_Area_EntryFirstClickMode = 2, value is “empty” (e.g. 0.00) - that zero is not selected, caret is where you clicked.
* ALP_Area_EntryFirstClickMode = 3, cell value does not matter: that click is not interpreted by the widget → cell value is selected, caret is at the end.

Note: the header divider line is drawn only when ALP_Area_HeaderMode is zero and appearance is Win10 or Pictures (11 = AL Use Pictures Interface).
AreaList Pro v10 always uses pictures when ALP_Area_HeaderMode is zero.
Either specified by developer (appearance = 11), created by native code (appearance = -1 = AL Native Interface) or the respective pictures for the chosen/resolved appearance from the Resources directory in the plugin’s bundle.

Example of a “formula” calculated column

AL_SetColumnTextProperty (area;column;ALP_Column_CallbackFnc;\
"\"Mr. \"*Num([People]Male)+(\"Ms. \"*Num(Num([People]Male)=0))\
+[People]First Name+\" \"+[People]Last Name)")

ALP_Column_Sortable allows the column to be sorted if the area allows sort with ALP_Area_UserSort = AL User sort on (1) or AL User sort index only (3) if the column displays an indexed field (or an array), or the sort to be bypassed with ALP_Area_UserSort = AL User sort bypass (2).

When a click occurs in the column header, AL Sort button event (-1) is reported if the column is sortable and ALP_Area_UserSort is not AL User sort off (0).
AL Column click event (-10) is reported in all other cases.

The column is “sortable” if ALP_Column_Sortable = 1 and the data allows sort (e.g. not a picture column or calculated column) and the header “cell” is directly associated with a column (e.g. not in a group header).

Set ALP_Column_MinWidth, otherwise the columns will be 0 points wide!

Two modes (values) are available for ALP_Area_AutoresizeAllColumns:

1 = List box style (shrink to fit):
• if there is enough space, nothing is resized
• if there is not enough space, all columns are sized to minimum (ALP_Column_MinWidth) and then columns from right are sized to normal size (if there is enough space) until the space is exhausted.
ALP_Column_Proportional is ignored in this mode.

2 = HTML like (proportional resizing of marked columns)
To have any effect, at least one visible column must have ALP_Column_Proportional set to 1!
Only visible columns with ALP_Column_Proportional property set to 1 are resized
The difference (shrink/expand) is distributed proportionally across the columns (if possible - honoring min/max width) using current column width
e.g. if you have one column with width 100, another one with width 200, the first one will get 1/3 of the resize, the second one will get 2/3 of the resize
If only one visible column has this property set, it behaves similarly to ALP_Area_AutoResizeColumn.

Example with value 2 (using ALP_Column_Proportional)
10 columns are set with their respective width. No matter how the width is set: computed from data (ALP_ColumnWidthUser = 0) or set by developer, or by user resizing the column.
3 columns out of these 10 have ALP_Column_Proportional set to 1.
When you grow “enough” the AreaList Pro area, 7 columns with “fixed” width will stay as they are, the other 3 (with ALP_Column_Proportional = 1) will be enlarged.
How much? Depends on the “fixed” width, and of course on the ALP_Column_MaxWidth values.
If these 3 columns are 40, 60 & 80 points, but the available space is 300 (the rest of the available space is used for the “fixed size” columns), they will be sized proportionally (assuming min/max width is not exceeded) to 66, 100 and 134.
In other words, you (or the user) set the basic width, but the actual width according to the (modified) area width is computed from the sum of the widths (of the “resizable” columns) and available width. Something similar is used when you shrink the area.
In that respect, you really need to set the ALP_Column_MinWidth to a usable value (default is zero).

	AL_SetAreaLongProperty ($1;ALP_Area_AutoHierarchy;1)  //Break on company name, create hierarchy
	AL_SetBreakTextProperty ($1;0;1;1;ALP_BreakCell_Value;"Total code for \\BreakValue")
	AL_SetBreakLongProperty ($1;0;1;1;ALP_BreakCell_ColSpan;3)  // span 3 columns
	AL_SetBreakLongProperty ($1;0;1;13;ALP_BreakCell_Source;14)  // use column 14 as source
	AL_SetBreakLongProperty ($1;0;1;13;ALP_BreakCell_ColSpan;2)  // span 2 columns
	AL_SetBreakTextProperty ($1;0;1;13;ALP_BreakCell_Value;"\\SUM")
	AL_SetBreakTextProperty ($1;0;0;1;ALP_BreakCell_Value;"TOTAL")
	AL_SetBreakLongProperty ($1;0;0;13;ALP_BreakCell_Source;14)
	AL_SetBreakLongProperty ($1;0;0;13;ALP_BreakCell_ColSpan;2)
	AL_SetBreakTextProperty ($1;0;0;13;ALP_BreakCell_Value;"\\SUM")

This makes the first cell in the break footer to span 3 columns (to display the whole value) and moves the total from column 14 to column 13 (it can be wide).
In other words, AL_SetBreakTextProperty ($1;0;1;14;ALP_BreakCell_Value;“\\SUM”) alone is enough to make cell 14 contain sum for column 14.
But if you want it in cell 13, you must set the cell source column to 14 (otherwise it would reference column 13 and it would use sum for column 13, not 14).