client-side wheel mouse support

remoting/proto/event.proto

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Protocol for event messages.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package remoting.protocol;
 
 // Defines a keyboard event.
-// NEXT ID: 3
 message KeyEvent {
   // The POSIX key code.
   required int32 keycode = 1;
   required bool pressed = 2;
 }
 
 // Defines a mouse event message on the event channel. 
 message MouseEvent {
 
   enum MouseButton {
     BUTTON_UNDEFINED = 0;
     BUTTON_LEFT = 1;
     BUTTON_MIDDLE = 2;
     BUTTON_RIGHT = 3;
     BUTTON_MAX = 4;
   }
 
   // Mouse position information.
   optional int32 x = 1;
   optional int32 y = 2;
 
   // Mouse wheel information.
+  // These values encode the number of wheel 'ticks' (or 'clicks').

[Wez, 2011/10/13 00:38:01]

nit: Consider explaining that "ticks" is the most consistent notion across
platforms, for now.

[garykac, 2011/10/13 21:18:53]

Done.

+  // TODO(garykac): Add support for high-resolution devices that give
+  // 'delta's that are accumulated to make a single tick.

[Wez, 2011/10/13 00:38:01]

nit: Remove the TODO, and instead just say "We may add fields to support
high-resolution scroll input."

[garykac, 2011/10/13 21:18:53]

Done.

   optional int32 wheel_offset_x = 3;
   optional int32 wheel_offset_y = 4;
 
   // Mouse button event.
   optional MouseButton button = 5;
   optional bool button_down = 6;
 }