diff -r ed1c9f64298a -r 5b9d4d8641ce trace/traceviewer/com.nokia.traceviewer.help/html/reference/preferencesgeneral.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceviewer/com.nokia.traceviewer.help/html/reference/preferencesgeneral.htm Wed Jun 23 14:49:59 2010 +0300 @@ -0,0 +1,57 @@ + + + +General settings + + + +

General settings

+

These preferences can be accessed from: Window > Preferences > Carbide Extensions > TraceViewer.

+

+ ++ + + + + + + + + + + + + + + + + +
General settings
    +
  • You can select whether there should be a number of milliseconds after +the previous traces after the timestamp of the current traces. If selected, +the amount of milliseconds from the previous trace is shown in brackets [ +] after the normal timestamp.
    • +
  • You can select if component and group names are shown before the trace text, if +those are available.
    • +
  • You can also view the class and function name before the trace text, if +those are available.
    • +
  • It's possible to select if changed Dictionaries are automatically reloaded.
    • +
  • You can select if you want BTrace variables to be shown after the trace text in OST traces. These contain possible CPU ID and Thread ID.
    • +
Timestamp accuracy
    +
  • Timestamp accuracy can be shown in milliseconds or microseconds.
    • +
Displaying undecoded traces

You can choose how undecoded traces are shown in the TraceViewer view. +Choices are:

    +
  • “BINARY TRACE” text: displays a text indicating that +the trace is binary and the decode file may not be loaded.
    • +
  • HEX: traces received are shown as a hexadecimal string. Each byte +is converted into a hex string and bytes are separated by spaces.
    • +
  • Identification numbers and data: TraceViewer will display component, +group and trace ID of the received trace. Also the data contained in the trace +is displayed as a hex string.
    • +
+ + + + \ No newline at end of file