When the Action Pending Window is displayed for a Debug statement, a Configure button is displayed. When clicked, a panel is displayed allowing you to change what content is displayed.
The panel displays items in the order they are displayed. The following items are available:
Action test state- The value of the action test state will be displayed under a header named: Action test state.
Action debug state- The value of the action debug state will be displayed under a header named: Action debug state.
- Call stack
- The call stack which lists every active call's location, execution mode (grouped or stepwise) and statement name, will be displayed. The first item displayed is at the top of the stack. The last is at the bottom. The header in the display is Call stack.
- Execution mode
- The execution mode, grouped or stepwise is displayed. If the mode is grouped, the current file and its File Index property are displayed as well. The header is Execution mode
- Initial files
- The set of available files when the action was first started. File availability statements can change the available files. The number preceding the file name is the File Index property which was in effect when the initial files were the active files.
- Active files
- The current set of available files is displayed. The File Index property precedes each name. Note that the set of active files is not changed when the execution mode is grouped. The header is Active Files
- Per track Content
- This controls the display of per track items. When executing grouped unless None is selected the items in the current track will be displayed. When executing Stepwise, the settings are interpreted as follows:
The Track information setting determines how content is displayed. The Include settings determine which content is displayed. You can elect to display the following types of items:
- None
- No per track items are displayed.
- Snapshot
- The snapshot displays a single set of values for the content across all selected files. If an item has more than one value across all tracks it will be displayed as:
... multiple values ....- Per Track
- If the items across all tracks are consistent, a snapshot is displayed. Otherwise track content for every file will be displayed.
- Both
- Same as Snapshot followed by Per Track. The snapshot is always displayed.
- Track Variables
- All non empty track variables will be displayed
- Properties
- Using the configure button (gear icon), you select which properties are to be displayed. Note that empty properties are not displayed. Boolean properties which are No are considered empty. Numeric properties which are 0 are considered empty.
- Fields
- Using the configure button (gear icon), you select which fields are to be displayed. All selected fields with a non empty value will be displayed. Note that the field display is a tag set. You can use the displayed table's context menu to perform the same set of functions you can in any displayed Tag Set.
- UDTIs
- Using the configure button (gear icon), you select which UDTIs are to be displayed. The set of available UDTIs is the list of all UDTIs currently in any active file and any UDTIs previously selected. All non empty selected UDTIs will be displayed. The displayed list can be empty.
- System variables
- Non empty system variables will be displayed. The header is System Variables.
- Named variables
- The complete set of non empty named variables will be dumped. The header is Named Variables
- Databases
- Potentially two lists. One of all open databases in the UI and another of all open query databases. The status information displayed is described in the Open Database Information statement.
- Containers
- A list of all defined containers.
- Show step information
- The Action Pending Window has always had the ability to display step information at the bottom of the panel. This is outside the scrollable content area of the panel. The step information includes the calling location, the step's name (Debug) and the file being manipulated which might be meaningless if the execution mode is stepwise. This information is largely redundant for the Debug statement, especially if the call stack is being displayed. It is included for continuity with other prompt category statements.
The content of variables can be quite large and may contain newline characters. The Compress content option replaces newline characters with \n and truncates content to a shorter length. Truncated content is followed by a … character. The View Debug Info in Log Viewer item on the disclosure button's menu always ignores this setting.
If Auto display Debug statement is set, the action containing the calling Debug statement will automatically opened and the Debug statement will be selected. This will be done when the Debug panel is first displayed as a result of executing the Debug statement.
Note that two copies of the configuration settings are retained: the current settings are those which will be displayed. The saved settings is a configuration which can be restored.
If you close the panel by the Done button, the current settings will be updated.
If you close the panel by the Save button, the current and saved settings will be updated.
If you close the panel by the Restore button, the saved settings will be copied to the current settings.
If you close the panel by the Cancel button, nothing will be modified.