From eadc9b790a731fc03a7a2318fa2df5025f97b722 Mon Sep 17 00:00:00 2001
From: beuc <beuc@7f0cb862-5218-0410-a997-914c9d46530a>
Date: Tue, 8 May 2012 17:28:38 +0000
Subject: [PATCH] Multi-touch precisions

git-svn-id: https://svn.code.sf.net/p/freeglut/code/trunk@1312 7f0cb862-5218-0410-a997-914c9d46530a
---
 freeglut/web-src/docs/api.php | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/freeglut/web-src/docs/api.php b/freeglut/web-src/docs/api.php
index 697cedf..9d79b4e 100644
--- a/freeglut/web-src/docs/api.php
+++ b/freeglut/web-src/docs/api.php
@@ -2160,8 +2160,12 @@ finger).<br />
 Exception: in MultiButtonFunc, the order of callback parameters is
 different (x,y,button,state instead of button,state,x,y).<br />
 
-The non-multi callback variants are also called on X11.<br />
-TODO: are both callbacks called on Windows as well?<br />
+Currently, under X11, the non-multi callback variants are also called
+on X11 for each event.<br />
+
+Currently, under windows, the first (oldest) touch point also controls
+the mouse cursor, which triggers the non-multi callbacks as
+usual.<br />
 
 <br />
 
@@ -2175,8 +2179,8 @@ desirable to get the device id as well in the following situations:
   unrelated action, not part of the touchscreen gesture (may not be
   possible on some platforms).</li>
 
-  <li>To investigate: avoid touch id conflicts between touchpad and
-  touchscreen on Android; a possible work-around is to shift the
+  <li>Avoid touch id conflicts between touchscreen and
+  touchpad/gamepad on Android; a possible work-around is to shift the
   device id in the touch id.</li>
 
 </ul>