> 'I am idle, I am active' vs 'I idled the day away, I activated the washing machine.' On the platform, change in state are reflected with an [INFINITIVE] event which changes the object to an [PAST-TENSE] state, e.g. "load" event -> "loaded" state, "activate" event -> "activated" state. That's why we're not using "active" as a state. Maybe "idle" isn't the right state name either, given that context. > I guess most want to know whether something is running or not running, whether to call start or stop. > > You know when it is active as you will get your first reading :). Well, you'll also get an "activated" event. That said, in the future, your first reading could be a cached reading, or it could also be a reading from your previous activation if we keep them around rather than replace them by `null` (there are arguments for both). -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/160#issuecomment-291083201 using your GitHub accountReceived on Monday, 3 April 2017 08:45:22 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:34:23 UTC