kdeconnect-kde/core/backends/bluetooth
Alexander Lohnau 49a51e2d27 Handle qDDebug/qCWarning categories more consistently
We can always provide a function rather than a value.
This is what we do in most places already and is consistent with the
rest of KDE.
This gets compiled to the same code.

```cpp
explicit QLoggingCategoryMacroHolder(const QLoggingCategory &cat)
{
    if (IsOutputEnabled)
        init(cat);
}
explicit QLoggingCategoryMacroHolder(QMessageLogger::CategoryFunction catfunc)
{
    if (IsOutputEnabled)
        init(catfunc());
}
```
2023-08-05 20:22:18 +00:00
..
bluetoothdevicelink.cpp
bluetoothdevicelink.h
bluetoothdownloadjob.cpp
bluetoothdownloadjob.h
bluetoothlinkprovider.cpp Handle qDDebug/qCWarning categories more consistently 2023-08-05 20:22:18 +00:00
bluetoothlinkprovider.h
bluetoothuploadjob.cpp Handle qDDebug/qCWarning categories more consistently 2023-08-05 20:22:18 +00:00
bluetoothuploadjob.h
CMakeLists.txt
connectionmultiplexer.cpp
connectionmultiplexer.h
multiplexchannel.cpp
multiplexchannel.h
multiplexchannelstate.cpp
multiplexchannelstate.h
Multiplexing protocol.md