On 11 June 2018 at 17:40, Dirk Hohndel <d...@hohndel.org> wrote:
>
>> On Jun 11, 2018, at 4:47 AM, Thiago Macieira <thi...@macieira.org> wrote:
>>
>> On Sunday, 10 June 2018 01:59:37 CEST Linus Torvalds 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.
lubomir
--
_______________________________________________
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
