This functionality is only available for certain module packages.

You are here: EEC > BASE > Debugging by means of the message protocol

Debugging by means of the message protocol

All actions executed by the user and resulting messages are entered in a message protocol. The message protocol stores the number of actions that has been defined in the user preferences. This means that, for example, only the last 100 actions are logged. Since actions produce a varying number of subactions and messages, the list may not only comprise the 100 actions, as configured, but also a large number of subactions and messages.

  1. To enhance the overview all actions are structured hierarchical and branches can be expanded and collapsed. New, unread actions and messages are displayed in bold, already read ones in regular.
  2. Decorators identify the severity level of a message.
  3. Errors are described in the Message / Description column.
  4. The status line contains the error-causing object.
  5. The error-causing object is listed in a table.
  6. By the context menu the error-causing object is navigated to.
  7. The error-causing object.
  8. The icons of the tool bar offer actions to expand and collapse branches and indicate all messages as read resp. as unread. and to filter messages with several criteria. Actions can be filtered with the criteria Error, Warning, Info and All other (including actions without sub actions).

More: