|Disabled object||If checked, the edited object won't be included (including its subobjects) into the running application. |
The list of all disabled PROMOTIC objects can be seen in the INFO system in the /System/DisabledObjects item.
Macro expression can be used for input (it is evaluated while the application is launching). Caution!This property affects other objects in the runtime (these may refer to this conditionally disabled object). Therefore it is evaluated on launch before others and also the Macro expression $.par cannot be used. It is prferable to use for example Macro expression $.cfgfile and this way use the configuration file to define which object will really be launched in the app.
|Object name||Name (identifier) of the PROMOTIC object. It is used for returning a reference to this object by the PmObject.Pm method. |
This configurator sets the initial value of the property Name.
This is a system name and must not contain diacritics, empty string, spaces and the first character must not be a number.
|Class||Type of the edited (marked) object in the objects tree. See property: ClassName.|
|The time of last editing||The saved time of last editing of the object. The value is set automatically to a current time when saving the edited PROMOTIC object. On the contrary, saving multiple objects simultaneously (the whole branch) will not cause the modification of this time in saved objects. |
This stored edit time can also be used for "Find object by edit time" operation, in object local menu.
|Object path||Name of the object including the full path in the objects tree. This text can be inserted as a first argument of the PmObject.Pm method. See property: PathName.|
|Object size and license||Displays a window with PROMOTIC object extended information. The number of variables, number of panels and licenses used in selected object and its subobjects. The number of variables is used to define application size. |
Variables that are counted into the total application size are in objects PmData, PmOpcClientData, PmTrend, PmCommData, PmCommMsg, in obsolete objects PmNumber and PmString and in ExtSubVar data extension.
The number of application variables expresses the extent and complexity of the application. The total number of application variables is the sum of all defined data variables of the application. According to the number of the variables, the license price is then defined. See Basic runtime license and Price list .
|Member of logical groups||The list of the identifiers of the logical groups (the comma ',' is the separator), the object belongs into (it is a group member), see Logical groups. The logical group selection can be done in the Member of logical groups window.|
|Object accessible via variable||Creation of the global variable (read only) with the reference to this object (in scripts, it is possible to refer to the object through this global variable). This configurator is considered obsolete and therefore it is hidden in new apps and in apps that did not use it.|
Yes, from object name
Yes, manually entered name
|Name||Name of the created global variable (if enabled) where the name can be laid from the prefix pmo and the object name or it can be entered manually. This is a system name and must not contain diacritics, empty string, spaces and the first character must not be a number.|
|PROMOTIC object parameters||Allows to enter the PROMOTIC object parameters (the "bubblingů system allows the parameter accessibility also for its subobjects). See Parameters of the PROMOTIC object. |
It is a text in format PmNamedValues.
Caution for prototypes and instances: The PmInstance object can receive only the parameters from the corresponding PmPrototype object, and can enter modified values there. I.e. the instance can modify the existing parameter values of the corresponding prototype. The instance, or the instance parents, cannot add new parameters. Instance (prototyp) can access only the parameters defined in the prototype, but cannot access the parameters of instance parent. This way it is ensured that all instances of the individual prototype has the same set of parameters with different values. The PmInstance object is therefore special from the parameter searching (bubbling) point of view, because the parameter search is terminated there and does not continue to the PmInstance object parent. This way the instance of the prototype is isolated from other parameters present in the application. If it is necessary to obtain the value of the parameter for the prototype from the instanece parent, then the parameter must be created in the PmPrototype object (the name can be the same or different) and refer to the parameter of the instance parent either here or in the PmInstance object. The reference to the parent parameter is done by Macro expression $.par in the parameter value in the instance or prototype.
For example in the prototype, create a new parameter boiler, and link the value to the boiler parameter value of the instance parent: boiler:$.par("boiler");
|User description||User defined PROMOTIC object description. It allows the application designer to write down his notes or documentation directly into the PROMOTIC object. This type of documentation simplyfies the future maintenance of the application and orientation, especially for other developers. The user defined description is saved in the form of formatted text, may contain highlighting, new rows or links to another PROMOTIC objects. |
The Links button allows to move between the PROMOTIC objects with user defined description easily. A window is displayed containing the object tree, where the objects containing the user defined descriptions are indicated as bold.
The source form: the user generated description is written in the form of XML syntax, where the formatting is indicated by special marks. The Edit button enables the edit mode. The "User description" window window is displayed.
The displayed form: the user defined description is displayed for viewing in formatted from.