Add GetUsbKeyCode dev interface for Pepper key events

ppapi/cpp/input_event.h

Index: ppapi/cpp/input_event.h
diff --git a/ppapi/cpp/input_event.h b/ppapi/cpp/input_event.h
index 195ac08f3f14ac4116f68e33360e8fd1b0d28369..ce4aeb00ec0cc3e7afa3a0752f948608d2386b87 100644
--- a/ppapi/cpp/input_event.h
+++ b/ppapi/cpp/input_event.h
@@ -7,6 +7,7 @@
 
 #include <string>
 
+#include "ppapi/c/dev/ppb_keyboard_input_event_dev.h"
 #include "ppapi/c/ppb_input_event.h"
 #include "ppapi/cpp/resource.h"
 
@@ -300,6 +301,20 @@ class KeyboardInputEvent : public InputEvent {
   /// input events. For non-character input events the return value will be an
   /// undefined var.
   Var GetCharacterText() const;
+
+  /// PPB_KeyboardInputEvent_Dev interface.

[brettw, 2012/02/15 00:42:44]

I prefer not to have Dev interfaces in the C++ wrappers except in a dev
directory. In this case, I don't think it's a huge problem to just not bother
with C++ wrappers for the USB stuff. For the few people that want to test this
out, they can just call into the C API.

[Wez, 2012/02/16 19:18:51]

Agreed; the API is sufficiently simple that this shouldn't pose a problem.  As
for the C APIs, the C++ wrappers outside a dev/ sub-directory should only
contain stuff that calling code can rely on.

[garykac, 2012/02/16 20:45:03]

Done (patchset 13)

+
+  /// Sets the USB scancode for this key event. When the USB scancode is moved
+  /// out of _Dev, <code>usb_scan_code</code> will be added as a parameter
+  /// to <code>Create</code> and this method will be removed.
+  ///
+  /// @param[in] usb_scan_code The USB scancode that corresponds to the key
+  /// that generated this keyboard event.
+  bool SetUsbScanCode(uint32_t usb_scan_code);
+
+  /// Returns the USB scancode that corresponds to the key that generated this
+  /// keyboard event.
+  uint32_t GetUsbScanCode() const;
 };
 
 }  // namespace pp