'version' Directive

Syntax

//@version "version-string"

Description

Specifies Form API version, version-string can be one of the following:

Version	Notes
1.0	Initial version, deprecated, not supported in package 167 and later; see Calculation Model (v1.0) for details.
2.0	New form calculation model, see Calculation Model.
2.1	prompt() function's behavior has changed.
2.2	New server-side call syntax, server-side events, server-side batch operations model, support for user-defined control classes. Breaking change: Global MetaScript's `include` directives are executed before form views hierarchy is created.
2.3	CSS box model for groups
2.4	Changed: Form.GetField returns null for empty XDate/XTime instead of XDate/XTime with NaN as valueOf. FormInputElement.value converts NaN to null (was 2.5 before package168-1836) New: Server-side calls using callback syntax are executed asynchronously Removed: `meta_objectSaved` event Transactions on the client side RunSQLQuery on the client side
2.5	Web forms support and related cleanup: All database APIs moved to server side. Dropped "Calculate As"/"Default value" expressions. OldField function dropped also as a part of old calculation model. Form popup popup box is rendered by frame label removed MetaScript-filled list removed legacy popup wrapper and list removed Form.GetField does not convert XDate to Date and returns null for empty XDate and XTime. Dropped pattern fill. Finds: all type fields can be used in conditions (not limited to the fields present on the form). Browser Opens in chromeless mode by default through OpenURI( "vt://browser..." ), Finds or DR context menu. Properties dialog is not shown anymore (with the exception of Digital Resources). ID field can be edited for a new object (if it is present on the form). Form is not centered vertically in chromeless mode (centered horizontally only).

Example

Setting Form API version to 2.2 to enable the new server-side call syntax:

'version' Directive

Syntax

Description

Example

See Also

Labels