`Qt` message logging may be tricky

If you handle the `Qt` messages to print those in the widget, the widget may report a `Qt` message internally while adding an entry, thus blocking the application execution. We need to somehow block all the `Qt` messages from the widget.

Start by tracing the widget's Qt message handling and the code path that adds an entry. Reproduce the recursive logging and application-blocking behavior described, then verify that messages emitted during widget updates no longer interrupt execution.

Written by the indexing model from the issue text.