Controller QJSEngine: Several Console API commands doesn't behave as expected

[JoergAtGithub]

Bug Description

Mixxx uses the console apie extension of the QJSEngine for controller mappings ( https://doc.qt.io/qt-5/qtquick-debugging.html#console-api )

While working on #4718 I noticed that several console functions don't work as expected:

• console.trace() No output at all
• console.assert(condition, message) Expected output in the console with --controller-debug (critical message followed by stack trace) but no error dialog.
• console.exception(message) Expected output in the console with --controller-debug (critical message followed by stack trace) but no error dialog.

Version

2.4

OS

Windows 11

[Swiftb0y]

Maybe the output of those is somehow tied to the log-level?

[JoergAtGithub]

I found out, that console.trace() doesn't use the logging category "js", as the as console commands, but "default".

If I add the category name "default" as additional condition to

mixxx/src/util/logging.cpp

Lines 47 to 54 in e231c56

	if (categoryName == jsLoggingCategory ||
	categoryName.substr(0,
	std::min(categoryName.size(),
	controllerLoggingCategoryPrefix.size())) ==
	controllerLoggingCategoryPrefix) {
	// If the logging category name starts with `controller.`, show debug messages.
	category->setEnabled(QtDebugMsg, true);
	} else {

the output of console.trace() works.

But I could imagine, that this generates spam elsewhere.

[JoergAtGithub]

https://bugreports.qt.io/browse/QTBUG-108673