21388 2013-03-25 12:51:48 +0000 handling of analog vs. digital buttons 2013-10-11 16:28:52 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Gamepad unspecified All All RESOLVED FIXED P2 normal --- 1 ted ted mike public-webapps scott.w3bugzilla public-webapps-bugzilla oldest_to_newest 84920 0 ted 2013-03-25 12:51:48 +0000 Currently the spec represents buttons as an array of double values, to handle analog buttons (like the trigger buttons on most modern gamepads). However, I'm starting to think this might not be sufficient. The Playstation 3 controller, for example, has pressure-sensitive buttons which provide both a digital (pressed/not pressed) and an analog (how hard is it being pressed) value. It seems like it would be unfortunate to lose part of that data. Should we spec button values to include both a boolean and a double value? 94561 1 ted 2013-10-10 18:14:21 +0000 The recently-unveiled Gamepad framework in iOS 7/OS X 10.9 exposes buttons as a pressed+value pair: https://developer.apple.com/library/ios/documentation/GameController/Reference/GCControllerButtonInput_Ref/Reference/Reference.html#//apple_ref/doc/c_ref/GCControllerButtonInput 94590 2 ted 2013-10-11 16:28:52 +0000 I changed the buttons[] attribute to be of type GamepadButton, which has both pressed and value attributes: https://dvcs.w3.org/hg/gamepad/rev/a37c10a031b4 This is the only breaking change I wanted to make to the spec.