[Remoting Android] Use floating point coords for rendering the cursor

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

Index: remoting/android/java/src/org/chromium/chromoting/SimulatedTouchInputStrategy.java
diff --git a/remoting/android/java/src/org/chromium/chromoting/SimulatedTouchInputStrategy.java b/remoting/android/java/src/org/chromium/chromoting/SimulatedTouchInputStrategy.java
index f7e9263fe514c95933d719fe07af892d061e1936..694ea6aa77bbe18dd8811d149760500fa631b8e0 100644
--- a/remoting/android/java/src/org/chromium/chromoting/SimulatedTouchInputStrategy.java
+++ b/remoting/android/java/src/org/chromium/chromoting/SimulatedTouchInputStrategy.java
@@ -155,7 +155,7 @@ public class SimulatedTouchInputStrategy implements InputStrategyInterface {
 
     private Point getCursorPosition() {

[joedow, 2016/08/17 17:08:15]

Why not use the floating point cursor position everywhere?

IIRC we need to use int when sending the cursor pos to the remote machine, but I
think being consistent internally (in the client) will reduce the likelihood of
float->int->float precision loss bugs.

[Yuwei, 2016/08/17 17:42:45]

Done. Now using float everywhere and will convert them into int in
InputEventSender.

         synchronized (mRenderData) {
-            return mRenderData.getCursorPosition();
+            return mRenderData.getIntegerCursorPosition();
         }
     }