Classes | |
| class | BluetoothAdapter |
| One BlueZ adapter (org.bluez.Adapter1), e.g. More... | |
| class | BluetoothAdapterModel |
| List model over a BluetoothHost's adapters. More... | |
| class | BluetoothAgent |
| Implements org.bluez.Agent1, the pairing agent BlueZ calls back into during a Pair() handshake. More... | |
| class | BluetoothDevice |
| One BlueZ device (org.bluez.Device1), e.g. More... | |
| class | BluetoothDeviceModel |
| List model over a BluetoothHost's devices, optionally scoped to a single adapter. More... | |
| class | BluetoothHost |
| Facade over org.bluez: enumerates adapters and devices. More... | |
Functions | |
| PHOSPHORSERVICEBLUETOOTH_EXPORT void | registerQmlTypes () |
| Register every PhosphorServiceBluetooth QML type under the Phosphor.Service.Bluetooth module at version 1.0. | |
| PHOSPHORSERVICEBLUETOOTH_EXPORT void PhosphorServiceBluetooth::registerQmlTypes | ( | ) |
Register every PhosphorServiceBluetooth QML type under the Phosphor.Service.Bluetooth module at version 1.0.
Idempotent on repeat calls: internally guarded by std::call_once so a hot- reloading shell that builds a fresh QQmlEngine per reload can safely call this from every engine setup without triggering Qt's duplicate-registration warning.
Called from the consuming binary (typically phosphor-shell/src/main.cpp for the reference shell, but any QGuiApplication that wants to expose BlueZ to its QML can call this) before any QQmlEngine loads a .qml file. Keeping registration in the lib lets the consumer stay free of the type-registration boilerplate while still controlling when the types appear in their engine.