Since a few years now we also output Qt messages to the console by using qInstallMessageHandler() in mitk::BaseApplication. The issue is that Qt error and warning outputs that happen during normal operation like the infamous OpenGL context warning at application start irritate our users and they tried to connect other issues with those outputs multiple times. I'd like to make the output optional by introducing a command-line argument /Qt.logMessages resp. --Qt.logMessages.