diff options
| author | Juha Vuolle <juha.vuolle@insta.fi> | 2021-06-08 16:46:33 +0300 |
|---|---|---|
| committer | Juha Vuolle <juha.vuolle@insta.fi> | 2021-06-15 11:36:05 +0300 |
| commit | f8445fdcbf75e455443304bc290c48c37961e9f1 (patch) | |
| tree | 2e47f5185cd12f2fad8dfc28649dee21f1754265 /src/sensors/doc/src | |
| parent | 54b3ca67ad7230a21d76c581dd4287401acb230f (diff) | |
Make sensor possible to indicate it is no longer busy
The current implementation allowed sensor backend to only indicate
that it is busy, but not to tell when it was freed again. This commit
allows sensor backend to indicate also that it's busy state has cleared.
It is up to the sensor implementation to decide if it makes sense /
is possible to do that or not.
Pick-to: 6.2
Task-number: QTBUG-92513
Task-number: QTBUG-92505
Change-Id: Ied4857850e81346031fd83aa347d9955081118e8
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Diffstat (limited to 'src/sensors/doc/src')
| -rw-r--r-- | src/sensors/doc/src/qt6-changes.qdoc | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/src/sensors/doc/src/qt6-changes.qdoc b/src/sensors/doc/src/qt6-changes.qdoc index 7baad9f0..f71cde15 100644 --- a/src/sensors/doc/src/qt6-changes.qdoc +++ b/src/sensors/doc/src/qt6-changes.qdoc @@ -66,4 +66,17 @@ The property name is now aligned with the \c frontLidClosed property of the same QML type. + \section2 QSensorBackend::sensorBusy() and QSensor::isBusy() + + The \c QSensor::busy property and its accessor, \c QSensor::isBusy(), can be used + to check if the sensor is busy or not. To allow this property to better reflect the + sensor backend's state, QSensorBackend::sensorBusy() now accepts a boolean parameter. + This \c busy parameter is used to set/unset the backend busy state and notify the + QSensor interface attached to it. + + The default value for the QSensorBackend::sensorBusy() parameter is \e true which + results in the original behavior (except the added signal emission). This means + that in most if not all cases the changes are not mandatory. Instead it is up to the + individual sensor backend implementations to decide if the changes are useful. + */ |