Manage system debug options.
pSystemSettings ( in vlOperation,
in vlSettingValue )
|vlOperation||The operation requested.|
|vlSettingName||The name of a specific setting.|
|vlSettingValue||The value to be assigned to the setting.|
The pSystemSettings setting manages various debug settings. Settings can be maintained between Zim sessions, enabling you to define a standard debug environment that is restored every time you start Zim. These settings are stored in the registry file.
Settings managed by pSystemSettings include configuration options (most are read only), Zim debug options (e.g. LEXTRACE, SET TRACE OUTPUT), Framework tracing, and so on. You can enable or disable pSystemSettings. When it is disabled, the changes you make to settings (see EDITCONFIG, EDITTRACE, and EDITDEBUG below) are not reflected into your actual Zim environment. If pSystemSettings is enabled, then any changes you make are also reflected back.
The operations supported (passed in vlOperation) are
|INITIALISE||If you have previously saved your settings (see SAVE below), they are reloaded and settings are established (if pSystemSettings is enabled). If you do not have previously saved values, default settings are established.|
|EDITCONFIG||A dialog appears showing some of your current configuration options. From this dialog, you can also access windows displaying trace and debug settings. You can also enable or disable pSystemSettings. If pSystemSettings is enabled, any changes are reflected back to your Zim environment.|
|EDITDEBUG||A dialog appears showing various debug options. From this dialog, you can also access windows displaying trace and configuration settings. You can also enable or disable pSystemSettings. If pSystemSettings is enabled, any changes are reflected back to your Zim environment.|
|EDITTRACE||A dialog appears showing trace options. From this dialog, you can also access windows displaying configuration and debug settings. You can also enable or disable pSystemSettings. If pSystemSettings is enabled, any changes are reflected back to your Zim environment.|
|SET||This operation sets the value for a specific setting. The setting to be affected is passed in vlSettingName and can be any of the following: ERRORTRACE, SPYWINDOW, CHECKSETS, DEPENDENCY, ERRORS, INFORMATION, MEMBERCOUNT, QUOTING, RUNTIME, SINGLESTEP, STOPERRORS, WARNINGS, XREF, OBJECTMANAGER, DESIGNERSTATUS, FRAMEWORKTRACE, COMMANDTIMING, FLOW, LEXTRACE, STRATEGY, TRACE, TRACEOUTPUT, or TRANSACTIONFLOW. Most of these relate to Zim debug settings except for SPYWINDOW (enable or disable event/action spy window), OBJECTMANAGER (enable or disable ZOM), DESIGNERSTATUS (enable or disable the DC Application Design Status window), and FRAMEWORKTRACE (enable or disable Framework tracing). The setting value is passed in vlSettingValue which accepts ON, YES, Y, 1, TRUE, $TRUE, or T as “enable” values. TOGGLE causes the setting value to be toggled (enable if disabled or disable if enabled). Any other value causes the setting to be disabled.
If pSystemSettings is enabled, the change is reflected back to your environment.
|SAVE||This operation causes current settings to be saved. The next INITIALISE or LOAD operation (even in a different Zim session) restores these settings.|
|LOAD||Settings that were previously SAVEd are restored. If pSystemSettings is enabled, the new settings are reflected to your environment.|
|RESET||This operation resets settings to default values and does a SAVE. If pSystemSettings is enabled, the new settings are reflected to your environment.|
|SYNC||If pSystemSettings is enabled, the current settings are reflected to your environment.|
|TOGGLE||If pSystemSettings is enabled, it becomes disabled. If pSystemSettings is disabled, it becomes enabled and a SYNC operation is performed.|
|ENABLE||pSystemSettings enabled and a SYNC operation is performed.|