[PATCH inputproto] XI2: swap (Raw)TouchUpdate and (Raw)TouchEnd

[Peter Hutterer]

Not having the event codes in the order begin/update/end does my head in
when debugging. It also means there's no symmetry between raw and normal
touch events as the ownership event is wedged in between.
Rearrange event codes to be Begin/Update/End for both, with the
OwnershipEvent being in between.

Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
---
I realise this isn't something we really _need_ but I still think it's the
better thing to do.

 XI2.h |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/XI2.h b/XI2.h
index cdd09ff..d31bb5c 100644
--- a/XI2.h
+++ b/XI2.h
@@ -188,13 +188,13 @@
 #define XI_RawButtonRelease              16
 #define XI_RawMotion                     17
 #define XI_TouchBegin                    18 /* XI 2.2 */
-#define XI_TouchEnd                      19
-#define XI_TouchOwnership                20
-#define XI_TouchUpdate                   21
+#define XI_TouchUpdate                   19
+#define XI_TouchEnd                      20
+#define XI_TouchOwnership                21
 #define XI_RawTouchBegin                 22
-#define XI_RawTouchEnd                   23
-#define XI_RawTouchUpdate                24
-#define XI_LASTEVENT                     XI_RawTouchUpdate
+#define XI_RawTouchUpdate                23
+#define XI_RawTouchEnd                   24
+#define XI_LASTEVENT                     XI_RawTouchEnd
 /* NOTE: XI2LASTEVENT in xserver/include/inputstr.h must be the same value
  * as XI_LASTEVENT if the server is supposed to handle masks etc. for this
  * type of event. */
-- 
1.7.7