Can't see controllerDebug messages when built with qdebug off

[Sean M. Pappalardo]

When building Mixxx with qdebug=0 (and build=release) on Linux, running with --controllerDebug does not show any output. Maybe that's obvious but we need a way for that option to still work since users need it for controller preset development.

[Daniel Schürmann (daschuer)]

I will redirect all related qDebug() calls to QDebug().

I am afraid we have the same issue for Skin debug.
What would be the drawback if we do not disable debug for our release?

[Sean M. Pappalardo (pegasus-renegadetech)]

Oh, I didn't intend for anyone to work on this now! I filed it while I was thinking about it so it could be considered later. (I also originally thought we were going to disable qDebug in this release, but we're actually not planning to do so any time soon, hence the 'Low' priority and no milestone targetted.)
The reason we would disable it is to prevent the overhead of printing messages to the console and into the log file.

[Sean M. Pappalardo (pegasus-renegadetech)]

Wait, when was this fixed?

[RJ Skerry-Ryan (rryan)]

https://github.com/mixxxdj/mixxx/pull/808

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8372