informational messages (messages that do not require action)
Generally, you will use LOGINFO to log detailed error and other informational messages. You will use LOGGER to capture your debug messages to the log file.
NFO logs an informational message if the logging token exists in the Shared memory.
In this case, you see 5 informational messages.
It begins by creating a request object and then popping up an informational message box.
While the informational message is a very simple widget - it does not use events or expose new methods - it should give you enough of an idea of how widgets operate.
You should see an informational message box telling you that the pattern was applied successfully.
This means that informational messages will not be traced, but you will still receive any error messages.
To dispel the magic behind widgets, let's develop a very simple widget that displays informational messages.
Errors (both fatal and non-fatal), warning, and informational messages are logged, while the adapter's data and control flow information is traced in the tracing configuration.
You can add validators on attributes, units, capabilities, and domains, and you can report the status to the model user as an informational message, warning, or error message.
If the attribute does not match the version number format, the validator applies an informational message to the unit.