Qt 5.11 | Qt Sensors | C++ Classes | QSensorManager

Qt 5.11.3 Reference Documentation

# QSensorManager Class

The QSensorManager class handles registration and creation of sensor backends. More...

Header: | #include <QSensorManager>
qmake: | QT += sensors

- List of all members, including inherited members

## Static Public Members

QSensorBackend * | createBackend(QSensor *sensor)
bool | isBackendRegistered(const QByteArray &type, const QByteArray &identifier)
void | registerBackend(const QByteArray &type, const QByteArray &identifier, QSensorBackendFactory *factory)
void | setDefaultBackend(const QByteArray &type, const QByteArray &identifier)
void | unregisterBackend(const QByteArray &type, const QByteArray &identifier)

## Detailed Description

The QSensorManager class handles registration and creation of sensor backends.

Sensor plugins register backends using the registerBackend() function.

When QSensor::connectToBackend() is called, the createBackend() function will be called.

## Member Function Documentation

### `[static]` QSensorBackend *QSensorManager::createBackend(QSensor *sensor)

Create a backend for sensor. Returns null if no suitable backend exists.

### `[static]` bool QSensorManager::isBackendRegistered(const QByteArray &type, const QByteArray &identifier)

Returns true if the backend identified by type and identifier is registered.

This is a convenience method that helps out plugins doing dynamic registration.

### `[static]` void QSensorManager::registerBackend(const QByteArray &type, const QByteArray &identifier, QSensorBackendFactory *factory)

Register a sensor for type. The identifier must be unique.

The factory will be asked to create instances of the backend.

### `[static]` void QSensorManager::setDefaultBackend(const QByteArray &type, const QByteArray &identifier)

Sets or overwrite the sensor type with the backend identifier.

### `[static]` void QSensorManager::unregisterBackend(const QByteArray &type, const QByteArray &identifier)

Unregister the backend for type with identifier.

Note that this only prevents new instance of the backend from being created. It does not invalidate the existing instances of the backend. The backend code should handle the disappearance of the underlying hardware itself.