Controllers: Use console.log instead of engine.log

[Holzhaus]

Let's merge this uncontroversial change first. Reduces the PR size of #4523 and hopefully it will make the CI checks green, too.

[Swiftb0y]

LGTM Merge?

[ywwg]

style issues are existing old js problems, fine to ignore

[ywwg]

@Swiftb0y ok to merge

[JoergAtGithub]

For me console.log doesn't work. If I change common-controller-scripts.js back to engine.log the output from the script appears again.

[Swiftb0y]

Did you make sure to use --controllerDebug?

[JoergAtGithub]

Yes --controllerDebug was defined, I built latest Main from scratch, to ensure that it was not related to my code.
All messages of the C++ part of the controller system appeared. But the messages from JavaScript, where I use HIDDebug were missing in the output. I changed common-controller-scripts.js while Mixxx was loaded, and the HIDDebug messages appeared after the automatic reload of the mapping.

[Swiftb0y]

Did you try manually defining the logging category filter?
try this environment variable: QT_LOGGING_RULES="controller.*.debug=true;*.input.debug=false"

[JoergAtGithub]

No, but Jan fixed this already: #4612

[Holzhaus]

Did you try manually defining the logging category filter?
try this environment variable: QT_LOGGING_RULES="controller.*.debug=true;*.input.debug=false"

The issue is that console.log uses the js logging category instead of controller.*, and --controller-debug doesn't show that category yet.

See #4612.

So QT_LOGGING_RULES="controller.*.debug=true;*.input.debug=false;js.debug=true" would work, too.

[Swiftb0y]

Thank you. I just saw the PRs in the wrong order and didn't realize my comment was obsolete before I made it.