40.21 Application Messages
40.21.1 Overview ¶
In the Application messages area you configure how the program informs you about processing notes and critical runtime errors. Unlike the Notifications (see Chapter 40.15), application messages are directed at the person operating the program - they appear either as a dialog in the foreground or as a brief toast in the corner.
Even if application messages are disabled here, all events are still recorded in the error log - the configuration only controls UI visibility.
40.21.2 Activation ¶
| Field |
Description |
| Show application messages, e.g. when settings cannot be saved |
Globally enables or disables UI display. With the option disabled, processing runs silently - messages only land in the log |
40.21.3 Display Mode ¶
| Mode |
Behavior |
| Dialog window |
Modal dialog that forces attention - the user must confirm before they can continue using the application |
| Toast |
Brief toast in the corner that disappears on its own after a few seconds - does not interrupt the workflow |
| Do not show |
No UI display |
Default: Toast - clearly visible but not disruptive.
40.21.4 Filter ¶
| Field |
Description |
| Also show information notes (not only warnings and errors) |
When active: additionally shows purely informational messages. When off: only shows warnings and errors |
Default: off - only warnings and errors are shown. Information notes are often routine messages that do not necessarily require a display.
40.21.5 Which Events Trigger an Application Message? ¶
Typical triggers:
- Save errors when writing profiles, accounts or options - e.g. permission problems, full disk
- Account connection errors - e.g. expired credentials, server not reachable
- Required-field problems on save - e.g. missing backup directory with backup enabled
- Initialization problems on startup - e.g. missing license, blocked database
- Optional information notes - e.g. success messages after manual actions
Processing errors of individual emails (e.g. specific task errors) do not appear as application messages - they go directly into the error log and into the processing log of the affected profile.
40.21.6 Tip ¶
- For critical production setups, combine Dialog window + Email notification on malfunction (see Chapter 40.8.4) - this way both the operator at the PC and an absent administrator learn about problems