Make Chromoting client plugin always render at device DPI.

remoting/client/plugin/chromoting_instance.cc

Index: remoting/client/plugin/chromoting_instance.cc
diff --git a/remoting/client/plugin/chromoting_instance.cc b/remoting/client/plugin/chromoting_instance.cc
index 77cd55fdc4e10a4b4d8513f9701ef43f13215535..35a5db002a321ad973fe33fb01b80a7ad021708d 100644
--- a/remoting/client/plugin/chromoting_instance.cc
+++ b/remoting/client/plugin/chromoting_instance.cc
@@ -322,18 +322,13 @@ void ChromotingInstance::HandleMessage(const pp::Var& message) {
   }
 }
 
-void ChromotingInstance::DidChangeView(const pp::Rect& position,
-                                       const pp::Rect& clip) {
+void ChromotingInstance::DidChangeView(const pp::View& view) {
   DCHECK(plugin_message_loop_->BelongsToCurrentThread());
 
-  SkISize new_size = SkISize::Make(position.width(), position.height());
-  SkIRect new_clip =
-    SkIRect::MakeXYWH(clip.x(), clip.y(), clip.width(), clip.height());
-
-  view_->SetView(new_size, new_clip);
+  view_->SetView(view);
 
   if (mouse_input_filter_.get()) {
-    mouse_input_filter_->set_input_size(view_->get_view_size());
+    mouse_input_filter_->set_input_size(view_->get_view_size_dips());

[Sergey Ulanov, 2012/07/17 19:36:06]

Do we always send mouse position in DIPs?

[Wez, 2012/07/17 20:11:43]

We will always receive them from Pepper in DIPs, yes, although in future they
will be floats with sub-DIP resolution.

   }
 }
 
@@ -387,7 +382,7 @@ void ChromotingInstance::Connect(const ClientConfig& config) {
   // Construct the input pipeline
   mouse_input_filter_.reset(
       new protocol::MouseInputFilter(host_connection_->input_stub()));
-  mouse_input_filter_->set_input_size(view_->get_view_size());
+  mouse_input_filter_->set_input_size(view_->get_view_size_dips());
   input_tracker_.reset(
       new protocol::InputEventTracker(mouse_input_filter_.get()));