client-side wheel mouse support

remoting/client/input_handler.cc

 // Copyright (c) 2010 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.
 
 #include "remoting/client/input_handler.h"
 
 #include "remoting/client/chromoting_view.h"
 #include "remoting/proto/event.pb.h"
 #include "remoting/protocol/connection_to_host.h"
 
@@ skipping 37 matching lines @@
   protocol::InputStub* stub = connection_->input_stub();
   if (stub) {
     MouseEvent* event = new MouseEvent();
     event->set_button(button);
     event->set_button_down(button_down);
 
     stub->InjectMouseEvent(event, new DeleteTask<MouseEvent>(event));
   }
 }
 
+void InputHandler::SendMouseWheelEvent(int dx, int dy,
+                                       int clicks_x, int clicks_y, bool page) {
+  protocol::InputStub* stub = connection_->input_stub();
+  if (stub) {
+    MouseEvent* event = new MouseEvent();
+    event->set_wheel_offset_x(dx);
+    event->set_wheel_offset_y(dy);
+    event->set_wheel_clicks_x(clicks_x);
+    event->set_wheel_clicks_y(clicks_y);
+    event->set_wheel_by_page(page);
+
+    stub->InjectMouseEvent(event, new DeleteTask<MouseEvent>(event));

[Wez, 2011/03/16 11:40:40]

Niggle:  I'm not keen on "InjectXXX" as client-side functions - conventionally
it's the Host that "injects" events into the host system.

[garykac, 2011/03/16 20:43:43]

This is a side-effect of having a common stub interface that used on both sides:
host and client.

Advantage: only one interface file to update
Disadvantage: goofy names that are inappropriate for one side or the other

Albert was the big proponent of this. Since he's there in London, he can
probably give you a coherent argument in person. ^_^

+  }
+}
+
 }  // namespace remoting