W3C home > Mailing lists > Public > public-device-apis-log@w3.org > June 2017

Re: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency?

From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
Date: Thu, 01 Jun 2017 16:14:17 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-305543520-1496333656-sysbot+gh@w3.org>
@tobie You are absolutely right, what I wanted to address is that, lets say:

iOS, Ash in ChromeOS (10Hz) or Windows WM uses Accelerometer to get basic orientation info.

The web page that creates `new Accelerometer({frequency: 0.0005});`, would not set effective sampling frequency of the sensor, since HW is used by other components. [Windows API](https://msdn.microsoft.com/en-us/library/windows/desktop/dd318991(v=vs.85).aspx)  clearly states this use-case (SENSOR_PROPERTY_CURRENT_REPORT_INTERVAL).

GitHub Notification of comment by alexshalamov
Please view or discuss this issue at https://github.com/w3c/sensors/issues/209#issuecomment-305543520 using your GitHub account
Received on Thursday, 1 June 2017 16:14:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC