Type: User Story
Priority: P3: Somewhat important
Resolution: Out of scope
Affects Version/s: None
Fix Version/s: None
A factory is creating instances of the driver class. Either it should be a sub-class of QSensor or it (or the factory) should create the QSensor instance. This is to help facilitate hacks where the client knows what driver is being used and accesses driver-specific stuff.
Update the API bits.
Update the unit test to verify the API bits.
Update the Qt Simulator backend.
I think the Qt Simulator backend lives in a QtSimulator repo.
Is a sub-class of the appropriate type the most suitable way of doing this? Is some other system more suitable?
Can the system cope when driver classes stop being sub-classes of QSensorBackend?