[Chromoting] TouchInputHandler now listens to events in DesktopView

remoting/android/java/src/org/chromium/chromoting/TwoPointsEventParameter.java

+// Copyright 2016 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.
+
+package org.chromium.chromoting;
+
+import android.view.MotionEvent;
+
+/**
+ * An {@link Event} parameter to represent two {@link MotionEvent}s with a {@link dx} and a

[Jamie, 2016/06/09 16:42:17]

Drive-by: What are the semantics of @link when applied to a variable (as opposed
to a class) name? Do we need it here?

[Hzj_jie, 2016/06/09 18:08:16]

Oh, I am using a wrong syntax, which should be {@link #dx}.

+ * {@link dy} to indicate the distance between the points.
+ *
+ * {@link android.graphics.Point} and {@link android.graphics.PointF} are both mutable, so this
+ * class uses two floats instead.
+ */
+public final class TwoPointsEventParameter {
+    public final MotionEvent e1;

[Lambros, 2016/06/09 02:36:39]

event1 and event2

Not sure about dx and dy. Maybe xDelta or xDistance or distanceX ? Or leave them
as dx, dy - we've probably used those abbreviations elsewhere.

[Jamie, 2016/06/09 16:42:17]

dx and dy are very commonly used throughout the codebase to represent deltas. I
think that naming is fine.

[Hzj_jie, 2016/06/09 18:08:16]

Done.

[Hzj_jie, 2016/06/09 18:08:16]

Sure, both updated.

+    public final MotionEvent e2;
+    public final float dx;
+    public final float dy;
+
+    public TwoPointsEventParameter(MotionEvent e1, MotionEvent e2, float dx, float dy) {
+        this.e1 = e1;
+        this.e2 = e2;
+        this.dx = dx;
+        this.dy = dy;
+    }
+}