[w3c/gamepad] whole controller timestamp an avenue to late breaking bugs? (#88)

seems that, since the timestamp is for the whole controller, (the latest event), then if two events occur during a poll, you don't know which the time is for?

for buttons this isn't much of a problem, but for finding the rate of change of an axis you need the time the analogue value was read (or somehow a correct delta). so what might give the appearance of working, could reveal itself as an insoluble issue only when you are some significant way down the development path.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/88