- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Feb 2017 15:50:59 +0000
- To: public-device-apis-log@w3.org
So this API fills-in the buffer synchronously? While the batching API will do so async? Seems confusing. Do we really want to offer two different APIs for this? Won't we often be in a case where there might be more than one sample per AF? e.g. especially if a frame is delayed. Providing quaternions doesn't seem to be specific to DeviceOrientation, though. It seems like a data representation strategy for a vector plus acceleration combo. Would be useful elsewhere too, e.g. for gyroscopes. I need better clarity on which data representation is useful for which high and low level sensors, so we figure out how we organize this across all motion sensors in a consistant and coherent whole. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/170#issuecomment-282325398 using your GitHub account
Received on Friday, 24 February 2017 15:51:05 UTC