Rick Waldron
Rick Waldron
> It seemed to be "will not work except when it does work" based on my stupid test :) Unfortunately, yes. This is a particularly frustrating and hairy bug. @gnarf...
@domenic thanks for providing this distinction.
https://github.com/w3c/sensors/issues/21
I don't understand how the [example](https://github.com/w3c/sensors/issues/13#issuecomment-63352715) illustrates an approach that matches the title of this issue. As a side note, I'm curious to know what magnetometer device (or any sensor,...
> Do you need IC support for this? No, that's not what I meant—that's way too low level > cache the values Got it, this is interesting and I agree...
> (for example, onchange events emitted at 60 Hz and a sensor emitting values at 1,000 Hz) So for this example, there would be at least ~17 values between each...
> This implies that the batching is done in native code and then transferred to the JS context all at once. Yes, no dispute. My concern still stands: what if...
This is great, thanks for the follow up :)
### Accelerometer | Property Name | Value | | --- | --- | | `x` | g-force | | `y` | g-force | | `z` | g-force (if available) |...
This is definitely important and a hard lesson learned by Johnny-Five—which is currently in the planning process of migrating all sensor component classes to support changing frequency after a sensor...