On Thu, Jul 26, 2012 at 9:20 PM, Scott Graham wrote:
> There's no particular indication at the spec level to indicate stopping the
> gamepad polling, based on the assumption that it's an implementation detail.
> Maybe there should be some way for content to hint that though?
>
> I guess an impleme
On Thu, Jul 26, 2012 at 6:10 PM, Scott Graham wrote:
> On Thu, Jul 26, 2012 at 5:44 PM, Adam Barth wrote:
>
>> What triggers us to stop polling the gamepad? When the object returned
>> by getGamepads() gets garbage collected?
>
>
> Currently, when the renderer goes away (or more specifically, w
On Thu, Jul 26, 2012 at 5:44 PM, Adam Barth wrote:
> What triggers us to stop polling the gamepad? When the object returned
> by getGamepads() gets garbage collected?
Currently, when the renderer goes away (or more specifically, when all
renderers that are using the gamepad api go away).
>
>
What triggers us to stop polling the gamepad? When the object returned
by getGamepads() gets garbage collected?
Adam
On Thu, Jul 26, 2012 at 4:32 PM, Scott Graham wrote:
> Thanks Travis, that seems like the "least surprising" solution.
>
> I guess getGamepads() would be the preferred name by
Thanks Travis, that seems like the "least surprising" solution.
I guess getGamepads() would be the preferred name by analog with
getUserMedia() then.
On Thu, Jul 26, 2012 at 4:10 PM, Travis Leithead <
travis.leith...@microsoft.com> wrote:
> Going to a function-based design is typically preferab
Going to a function-based design is typically preferable (especially to making
an attribute non-enumerable). This is the approach taken by getUserMedia.
From: scot...@google.com [mailto:scot...@google.com] On Behalf Of Scott Graham
Sent: Thursday, July 26, 2012 4:02 PM
To: public-webapps@w3.org
C
