.active

2.5 .active

Defines whether the object is active, i.e. ready to accept input.

Definition

Data type

boolean
Access

get, set
changed event

yes

For the object application, .active can be used to define and to query whether the application is currently running. Changing this attribute from false to true starts the application. Changing the attribute from true to false terminates the application.

The attribute .active defines whether the edittext shall have the current focus.

In notepage, .active = true refers to the page which is actually on top. For all other notepages .active is false, meaning that this attribute can only have the value true for one single notepage.

.active can be used to define and request whether the timer is currently active. Changing this attribute from false to true starts the timer. Changing the attribute from true to false resets the timer and makes it inactive.

To activate the input mode through the application, the attribute .active in the object tablefield is available both indexed (see below .active [I,J]) and non-indexed (.active). The behavior for the non-indexed attribute .active is as follows:

Action	Current State	Reaction
active := true	Focus on sensitive field	Input will be activated, if it is not yet active. If the input mode is already active, nothing happens.
active := false	Focus on sensitive field	Input mode will be deacti-vated, if it is active. Other-wise nothing happens.
active := true / false	Focus on non-sensitive field	No reaction from the object. The Dialog Manager sets .active back at false.
active := true / false	Focus is not on a field in the tablefield, but on a corner or on one of the scrollbars.	No reaction from the object. The Dialog Manager sets .active back at false.
active := true	Tablefield does not have the focus.	The Dialog Manager sets .active back at false. Other-wise no reaction.
User activates input		.active is set at true.