- From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Mar 2017 14:04:19 +0000
- To: public-device-apis-log@w3.org
Could you share some of the use-cases for option 3? Giving the problem with knowing which sensors will be used and having sensors appear at runtime, it might make sense to make this less flexible for users, as most users will know before hand what sensors they are going to use during their app live cycle. When do you set up the size of the shared memory? I guess we could replace it when adding new sensors and just document that adding new sensors may affect data delivery. Btw [slightly off topic], something which is not clear from API point of view. Say I want to use a RelativeOrientationSensor and a Magnetometer to calibrate the heading every 15 seconds so save power. Right now it is not clear to me whether I should set the frequency very low for the Magnetometer or turn it on/off every 15. Like will I actually save power from the magnetometer or not? -- GitHub Notification of comment by kenchris Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-288087915 using your GitHub account
Received on Tuesday, 21 March 2017 14:04:31 UTC