README.touch
changeset 7127 5011ddf43295
parent 6987 7084af936d82
--- a/README.touch	Sun Apr 28 09:54:56 2013 +0200
+++ b/README.touch	Mon Apr 29 23:41:49 2013 +0200
@@ -28,14 +28,14 @@
 SDL_FINGERMOTION:
 Sent when a finger (or stylus) is moved on the touch device.
 Fields:
-Same as FINGERDOWN but with additional:
+Same as SDL_FINGERDOWN but with additional:
 event.tfinger.dx       - change in x coordinate during this motion event.
 event.tfinger.dy       - change in y coordinate during this motion event.
 
 SDL_FINGERUP:
 Sent when a finger (or stylus) is lifted from the touch device.
 Fields:
-Same as FINGERDOWN.
+Same as SDL_FINGERDOWN.
 
 
 ===========================================================================
@@ -52,7 +52,7 @@
 
 The number of touch devices can be queried with SDL_GetNumTouchDevices().
 
-A SDL_Touch may be used to get pointers to SDL_Finger.
+A SDL_TouchID may be used to get pointers to SDL_Finger.
 
 SDL_GetNumTouchFingers(touchID) may be used to get the number of fingers currently down on the device.
 
@@ -65,7 +65,7 @@
 
 To get a SDL_Finger, call SDL_GetTouchFinger(touchID,index), where touchID is a SDL_TouchID, and index is the requested finger.
 This returns a SDL_Finger*, or NULL if the finger does not exist, or has been removed.
-A SDL_Finger is guaranteed to be persistent for the duration of a touch, but it will be de-allocated as soon as the finger is removed. This occurs when the SDL_FINGERUP event is _added_ to the event queue, and thus _before_ the FINGERUP event is polled.
+A SDL_Finger is guaranteed to be persistent for the duration of a touch, but it will be de-allocated as soon as the finger is removed. This occurs when the SDL_FINGERUP event is _added_ to the event queue, and thus _before_ the SDL_FINGERUP event is polled.
 As a result, be very careful to check for NULL return values.
 
 A SDL_Finger has the following fields: