Andras Lasso

Yes, mouse modes are supported. Any further improvement ideas can be tracked in additional tickets.

I've had a fresh look at this. Using the recently added `slicer.app.showConsoleMessage()` method we can log to the application console (Slicer process output) without logging into the Python console -...

I've tested [logging of Qt, ITK, VTK messages into the Python log](https://github.com/lassoan/Slicer/tree/log-vtk-errors-to-python-console) and the result is quite nice:  It would make sense to add this feature to Slicer core....

I've implemented the new design that collects all messages (coming from Python, VTK, ITK, Qt, ... loggers) and displays them in the Python console. These messages could be hard to...

`coloredlogs` only works on an ANSI terminal, so we would need to implement ANSI control character sequences in the Python console to take advantage of that. It would be easier...

I've force-pushed the log redirection to the Python console. It is ready for review/testing. The feature allows displaying errors from all sources (not just from Python but VTK, ITK, QT,...

I'm thinking about committing this to make it easier for everyone to try it. (We can always update or revert the commit if it does not turn out to work...

Most of the issues have been resolved. Submitted issues/pull requests in the affected repositories for the few remaining extension icon problems: - https://github.com/KitwareMedical/OsteotomyPlanner/issues/128 - https://github.com/ALive-research/Slicer-Liver/pull/166 - https://github.com/NIRALUser/SPHARM-PDM/issues/78 - https://github.com/jamesobutler/ModelClip/pull/1

This will be a useful feature, but needs more work. I'm closing this PR to reduce the number of open PRs, but we are happy to reopen if you can...

There have been no updates and the issue is most likely a CERR limitation, so I'm closing this.