kdeconnect-kde/core/backends
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
..
bluetooth Handle qDDebug/qCWarning categories more consistently 2023-08-05 20:22:18 +00:00
lan Handle qDDebug/qCWarning categories more consistently 2023-08-05 20:22:18 +00:00
loopback Add explicit moc includes to cpp files 2023-07-30 07:27:45 +00:00
devicelink.cpp Add explicit moc includes to cpp files 2023-07-30 07:27:45 +00:00
devicelink.h Remove unused default destructors 2023-08-05 20:22:18 +00:00
linkprovider.cpp Add explicit moc includes to cpp files 2023-07-30 07:27:45 +00:00
linkprovider.h Remove unused default destructors 2023-08-05 20:22:18 +00:00
pairinghandler.cpp Add explicit moc includes to cpp files 2023-07-30 07:27:45 +00:00
pairinghandler.h Remove unused default destructors 2023-08-05 20:22:18 +00:00