Configuring Tracealyzer

You can configure Tracealyzer options through the Settings dialog (File > Settings). All application settings, with the exception of the Global Settings, are stored at the project level.

Available Settings:

General Settings – Configure settings for the active project.
Global Settings – Configure global Tracealyzer behavior.
Docking Settings – Configure docking behavior for Tracealyzer views.
Navigation Bar Settings – Customize the Navigation bar content.
RTX64 Settings – Configure settings specific to RTX64.

General Settings

The General Settings tab contains these options:

Setting	Description
Reopen last trace on startup	Opens the most recently viewed session on the next startup of Tracealyzer.
Remember layout	Retains the current window layout for the next time Tracealyzer is opened.
Menu location	Choose where the menu bar inside View windows should be located: Top Left Right Bottom
Trace directory	The location to which session data is saved. By default, this field is empty and data is saved to the local Documents folder.
Enable old Trace View	When enabled, the Trace View from previous Tracealyzer versions is used.

Global Settings

The Global Settings tab contains these options:

Setting	Description
Reopen last project on startup	A project is a per-user work environment, wherein Tracealyzer settings, including most view configurations and layouts, are saved. When enabled (default), the most recent project is reopened on the next startup of Tracealyzer. When not enabled, a dialog appears when Tracealyzer is started. Through this dialog you can: Choose a project to open Create a new project Delete an existing project
Send anonymous feedback	When enabled (default), feedback is sent to IntervalZero anonymously.
Show Welcome on startup	When enabled (default), the Tracealyzer Welcome Screen appears on startup.

Setting

Description

Reopen last project on startup

A project is a per-user work environment, wherein Tracealyzer settings, including most view configurations and layouts, are saved.

When enabled (default), the most recent project is reopened on the next startup of Tracealyzer.

When not enabled, a dialog appears when Tracealyzer is started. Through this dialog you can:

Choose a project to open
Create a new project
Delete an existing project

Send anonymous feedback

When enabled (default), feedback is sent to IntervalZero anonymously.

Show Welcome on startup

When enabled (default), the Tracealyzer Welcome Screen appears on startup.

NOTE: Global settings persist across projects.

Docking Settings

The Docking Settings tab contains these options:

Setting	Description
Layout mode	Choose a method for positioning new views in the Tracealyzer window: Default (automatic depending on number of open views) New tab at currently active document view
Floating	Choose a method for positioning floating tabs in the Tracealyzer window: Default (start floating views as floating) Start floating views docked as new tab
Window layout locked	When enabled, the current window layout is locked and used the next time Tracealyzer is started.
Float windows on top	When enabled, float windows appear on top of the view port.

Navigation Bar Settings

Through the Navigation Bar tab, you can toggle display of icons in the bar on/off. By default, all views/icons are selected. To hide a view/icon from the Navigation Bar, clear its selection.

RTX64 Settings

The RTX64 Settings tab contains these options:

Setting	Description
Include raw Monitoring Framework events	When enabled, this setting will force Tracealyzer to include Raw Monitoring Events in the Trace View. This adds a copy of every event visualized using the RTX64 Monitoring internal format. Raw Events are indicated by a light teal color in the Trace View and in the Event Log. Raw events may contain additional details that Tracealyzer normally abstracts away, such as low level handles and pointers. NOTE: If this setting is changed while a session is open, you must close and reopen the session in order for the new Raw Events behavior to take effect. IMPORTANT! Including raw events will significantly increase memory usage and loading time.
Custom Events	Configure how custom events — events generated using RtGenerateEvent — will be handled by Tracealyzer. Default Custom Event Format – determine how to handle all custom events that don't have individual parsing rules: Ignore: Do nothing with these events. Only the channel name will be visible, and will automatically be set to “Custom N” where N is the event Kind. Binary data, format as hex: Format the data using a hexadecimal representation. If a format string is not defined, the format “name = value, name2 = value2,…” is used. C string - Default 8-bit codepage: This treats the data as a C string (null terminated). C string - Unicode: This treats the data as a unicode C string (null terminated). C string - UTF8: This treats the data as a null terminated UTF-8 string. Custom Events Format File – specify a file containing parsing rules for individual custom event kinds (overriding the default format). The Help > Event Definitions Sample menu contains a sample file with various examples. See Defining Parsing Rules for Custom Events in Tracealyzer for more information.

Setting

Description

Include raw Monitoring Framework events

When enabled, this setting will force Tracealyzer to include Raw Monitoring Events in the Trace View. This adds a copy of every event visualized using the RTX64 Monitoring internal format. Raw Events are indicated by a light teal color in the Trace View and in the Event Log.

Raw events may contain additional details that Tracealyzer normally abstracts away, such as low level handles and pointers.

NOTE: If this setting is changed while a session is open, you must close and reopen the session in order for the new Raw Events behavior to take effect.

IMPORTANT! Including raw events will significantly increase memory usage and loading time.

Custom Events

Configure how custom events — events generated using RtGenerateEvent — will be handled by Tracealyzer.

Default Custom Event Format – determine how to handle all custom events that don't have individual parsing rules:
Ignore: Do nothing with these events. Only the channel name will be visible, and will automatically be set to “Custom N” where N is the event Kind.
Binary data, format as hex: Format the data using a hexadecimal representation. If a format string is not defined, the format “name = value, name2 = value2,…” is used.
C string - Default 8-bit codepage: This treats the data as a C string (null terminated).
C string - Unicode: This treats the data as a unicode C string (null terminated).
C string - UTF8: This treats the data as a null terminated UTF-8 string.
Custom Events Format File – specify a file containing parsing rules for individual custom event kinds (overriding the default format). The Help > Event Definitions Sample menu contains a sample file with various examples. See Defining Parsing Rules for Custom Events in Tracealyzer for more information.