Message handling, debugging

[hexabits]

There's no way of knowing offhand what messages are meant for the end-user and which are truly for debugging. Many errors are a mix of qDebug(), qWarning(), qCritical(), qFatal() and actual QMessageBox classes.

Should probably explicitly call QMessageBox for messages intended for the user, and define QT_NO_DEBUG_OUTPUT and QT_NO_WARNING_OUTPUT for release builds so that those calls are optimized away during compilation.

Also, see: Debugging Techniques

It suggests defining QT_MESSAGE_PATTERN to make debug messages more useful. I misread it as being a define, when it is in fact an environment variable.

Task List

• Remove NO_MESSAGEHANDLER. (See also: NifSkope.pro file cleanup #27)
• Promote any qDebug() and qWarning() calls which are meant for end user to qCritical() or higher, or a QMessageBox proper.
• Define QT_NO_DEBUG_OUTPUT (and possibly QT_NO_WARNING_OUTPUT) for release builds.

Invalid Tasks

• Define QT_MESSAGE_PATTERN for more informative debug output. Guess this is an environment variable, NOT a define.