> On Jun 11, 2018, at 7:44 AM, Lubomir I. Ivanov <neolit...@gmail.com> wrote: >>>> Your debug log doesn't actually have the IO that is done. That seems >>>> to be a Qt issue. We ask for debug output, and some versions of Qt >>>> will give that: >>>> >>>> QLoggingCategory::setFilterRules(QStringLiteral("qt.bluetooth* >>>> = true")); >>>> >>>> and others will apparently just ignore it. >>> >>> Ubuntu installs a global file that overrides. It's up to the user to >>> configure >>> what output they want to see, not the application. >>> >>> The above line needs to be set by the user in the QT_LOGGING_RULES >>> environment >>> variable. >> >> So on Windows all we need to do is set that environment variable >> to get the full debug output we want? >> > > i've added this in the _run.cmd for the test package posted in this thread: > set QT_LOGGING_RULES=qt.bluetooth*=true > > the same DLL outputs the qt.bluetooth* messages in a standalone > application, so it seems that problem only happens in Subsurface. > not sure why.
Well, I don't know how you build Qt and Subsurface in your binaries. But if a sample app built against the same DLLs does show the output... I'd start with commenting out our attempts to mess with the QLoggingCategory (we do this in qt-ble.cpp and subsurface-desktop-main.cpp) We also are using the messageHandler to intercept the qDebug messages. That might be something worth playing with. /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface