Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
5.1.0 Beta 1
-
None
Description
The current implementation of dataRate is useless and makes no sense.
Currently, one has to setDataRate first before getting anything besides 0 out of dataRate.
It should report 0 only when there is an error, or no way to get hardware rates. It should report what rate the hardware is actually using, or in the case of resampling, the rate at which is default or was previously set.
Attachments
Issue Links
- relates to
-
QTBUG-33293 availableDataRates -> crash and/or wrong values
- Closed