|Main language of runtime|| Setting the default national language that is used in the runtime of the PROMOTIC system application (if the component requesting localized text does not explicitly specify the different language). |
Language is determined with a text identifier, e.g. "en", "de", "ru" etc. - see Fully supported languages in the PROMOTIC system.
If the "develop" (development) identifier is selected then the language of the development environment is used. Note: The language for the development environment is set in the menu "Options > PROMOTIC settings" in the Development system language configurator.
This configurator sets the initial value of the property Pm.RtLang.
|All used languages||The list of all national languages supported by running application simultaneously. |
Language defined in the Main language of runtime configurator should also be listed in the list. If missing, it is added to the list automatically.
The meaning of the list is to inform the PROMOTIC system about languages which should be loaded into the memory on application startup. It makes optimalization of loaded languages into the memory possible because not used languages are not loaded into the memory. The list itself consist of abbreviations of languages separated with comma (,).
If the application is designed only for one language, then this configurator should be left empty.
This language list is also used by the PmWebLang object, offering the Web pages language versions into the Web server.
|Runtime regime without the licence key||The configurator defines the PROMOTIC application runtime behavior if there is no licence key present (see also PROMOTIC modes according to the licence).|
RtNone+DevNone - cannot be launched either to the development environment or to the runtime - The application cannot be launched either to the development environment or to the runtime.
RtFree1 - free runtime, application up to 30 variables and 10 graphic panels, START INTO THE DEVELOPMENT ENVIRONMENT - The application runtime will use the RtFree mode. The size of the application is in this case limited to 30 variables and 10 graphic panels max. This is a legal runtime for running a small application. See PmRtFree - Free runtime licence.
RtFree2 - free runtime, application up to 30 variables and 10 graphic panels, START INTO RUNTIME (start into development environment by holding the <Shift> key) - The application runtime will use the RtFree mode. The size of the application is in this case limited to 30 variables and 10 graphic panels max. This is a legal runtime for running a small application. See PmRtFree - Free runtime licence. The application always goes into the runtime mode on start. This mode is valid for real applications and "replaces" the HW key containing the runtime licence. By pressing the Shift key during the start of the application the option can be suppressed and the application is started in the development mode.
RtForDevFree - runtime for testing the applications up to 100 variables (default) - The application runtime will run in the RtForDevFree mode. It is designed as a supplement to the DevFree development mode, that allows to develop an application up to 100 variables for free. This mode contains the warning windows and time limitation of the application runtime up to 1 hour. It is not designed for running a real application. It is designed for developing an application to be runned with PmRtFree or PmRtLite.
RtAppDemo - demo runtime, unlimited application size - The application runtime will run in the RtAppDemo mode. This mode allows to launch an application of any size for demo purposes. This runtime contains the warning windows and a time limitation up to 1 hour. It is not designed for running a real application.
|Runtime helps path||Path to the help file (*.hlp) that is called in the running application after pressing the Help key of the window. The file can be listed by the button. See: How to call user helps in application.|
|Panels timer period||Period in seconds with which active panels of the application are refreshed. Only those panels that haven't set the configurator PmPanel > Setup of the Options default values > Refresh period (refresh) will be refreshed. The preset value is 0.5 sec. |
This configurator sets the initial value of the property Pm.Blinker.
The period defined here affects only the local panels of the application. The period of WEB panels is defined in configurator PmPanel > Web Server > Refresh period of HTML pages [s].
|Password for editing the application||Setting the authorization for editing the application in the development environment. If the password is used and the authorization fails, the application editor does not open. See The authorization of editing the application. This is used for preventing opening and vieweing of the application content by unauthorized persons. In order to protect the runtime mode of PROMOTIC application - see Pm.LicenceInfo property.|
|Stop application runtime with confirmation||If checked, then on stopping the application runtime the confirmation window is displayed|
|Paths to system folders|
|To system data files||Path to system data files, i.e. files generated directly by the running PROMOTIC system. In particular the LOG files (see [Log]). |
This configurator is preset to #app:, i.e. the application folder.
|#appres: - to resources (resources: jpg,gif,avi,wav,...)||Path to application resources, i.e. to files of the type: |
- film (avi, mpeg, divx ...) - used for example by PmiWAnimate graphic item.
- sound (wav) - used for example by Pm.PlaySound method.
The path is used if the files are not found on defined paths or in the application folder. For getting this path, it is possible to use #appres:.
|#data: - to data files||The path to data files of the application. It is suitable to store any data files on this path. For getting this path, it is possible to use #data:. On some places this path is preset: |
- for alarms for files with the extension *.al/*.dbf to the subfolder Alarm (#data:Alarm/). See the configurator "Folder for files".
- for events for files with the extension *.ev/*.dbf to the subfolder Event (#data:Event/). See the configurator "Folder for files".
- for trends for database files to the subfolder Trend (#data:Trend/). See the configurator "Backup (table) name prefix".
|#cfg: - to configuration files||The path to configuration files of the application. It is suitable to store files with configuration information on this path (the information that doesn't change too much - in opposite to #data:). For getting this path, it is possible to use #cfg:. On some places this path is preset (by a macro): |
- for trends for files with the extension *.tg in the preset event of the buttons "Read"/"Store" of the Trend viewer with header graphic item.
|#temp: - to temporary files||Path to temporary and auxiliary application files.|
|Localized texts manager||Opens the window that is used for managing localized application texts: Localized texts manager|
|Manager of configuration files||Opens window for managing application configuration files: Manager of configuration files|
|Application backup manager||Opens window for application backups management: Application backup manager|