According to the source code, the debug messages come from:
DEBUG_MSG
which calls:
qCDebug(QTMIR_SURFACES).nospace()
So that sounds reasonable. It would appear at some point we will need to define QT_NO_DEBUG_OUTPUT during QtMir builds to stop excess debug messages in release binaries. Or to remove any truly excessive debug messages like those above which can appear on simple cursor movements.
According to the source code, the debug messages come from: QTMIR_SURFACES) .nospace( )
DEBUG_MSG
which calls:
qCDebug(
So that sounds reasonable. It would appear at some point we will need to define QT_NO_DEBUG_OUTPUT during QtMir builds to stop excess debug messages in release binaries. Or to remove any truly excessive debug messages like those above which can appear on simple cursor movements.