• spiiroin's avatar
    [hybrisadaptor] Refactor sensor start/stop logic · 8fab5538
    spiiroin authored
    Whether sensors should be started or stopped depends on a number
    of state variables. Using case specific conditionals at places
    where state variables might change makes the code fragile and
    hard to maintain.
    
    Separate sensor hal operations more clearly from logic and forms
    dictated by sensorfwd conventions.
    
    Use m_memberName naming convention for member variables, make
    all member data private and usable only via accessor functions.
    
    Use a single sensor start/stop policy evaluation function and
    call it from each place where relevant state variables might
    change.
    
    Use sensorfwd specific logging functions instead of qDebug etc.
    Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
    8fab5538
Name
Last commit
Last update
LuneOS Loading commit data...
adaptors Loading commit data...
c-api Loading commit data...
chains Loading commit data...
config Loading commit data...
config.tests/hybris Loading commit data...
core Loading commit data...
datatypes Loading commit data...
debian Loading commit data...
doc Loading commit data...
examples Loading commit data...
filters Loading commit data...
include Loading commit data...
qt-api Loading commit data...
rpm Loading commit data...
sensord Loading commit data...
sensors Loading commit data...
tests Loading commit data...
COPYING Loading commit data...
README.md Loading commit data...
TODO Loading commit data...
common-config.pri Loading commit data...
common-install.pri Loading commit data...
common.pri Loading commit data...
makedist Loading commit data...
sensord-qt5.pc Loading commit data...
sensord.conf Loading commit data...
sensord.init Loading commit data...
sensord.pc Loading commit data...
sensord.prf Loading commit data...
sensorfw.conf Loading commit data...
sensorfw.pro Loading commit data...