specs: remove xtest1.info, no longer relevant

This appears to be a text snippet regarding an implementation note
on the x11 input synthesis extension. The function referenced
can be found in the hw/hp/input directory of the server
in the xext1imp.c file.

http://195.113.144.229/MIRRORS/ftp.xfree86.org/pub/mirror/X.Org/pub
/R6.6/xc/programs/Xserver/hw/hp/input/xtest1imp.c

Signed-off-by: Gaetan Nadon <memsize@videotron.ca>

2 files changed, 0 insertions, 92 deletions

diff --git a/specs/Xext/Makefile.am b/specs/Xext/Makefile.am
index 44d32c9..6cdb477 100644
--- a/specs/Xext/Makefile.am
+++ b/specs/Xext/Makefile.am
@@ -6,6 +6,4 @@ dist_xml_DATA = $(doc_sources)
 
 include $(top_srcdir)/xmlrules.in
 
-EXTRA_DIST = xtest1.info
-
 endif ENABLE_SPECS
diff --git a/specs/Xext/xtest1.info b/specs/Xext/xtest1.info
deleted file mode 100644
index aa28302..0000000
--- a/specs/Xext/xtest1.info
+++ /dev/null
@@ -1,90 +0,0 @@
-XTestGenerateEvent is supposed to cause the server to generate a key or
-button event, exactly as one would be generated if a user pressed a key
-or pushed a mouse button.  Without knowing how your server does that for
-normal input events, I can't tell you exactly how that should look, but 
-it would be something like:
-
-void
-XTestGenerateEvent (dev_type, key_or_button_code, direction, x, y)
-    int dev_type;		/* MOUSE = X pointer, KEYBOARD = X keyboard */
-    int key_or_button_code;	/* code to stash in event */
-    int direction;          	/* XTestKEY_UP or XTestKEY_DOWN */
-    int x,y;			/* location of event  */
-    {
-    int type;
-    xEvent *xE;		
-
-    if (key_or_button_code < 8)		/* must be a button */
-	if (direction == XTestKEY_UP)	/* it's a release event*/
-	    type = ButtonRelease;
-	else
-	    type = ButtonPress;
-    else				/* must be a key */
-	if (direction == XTestKEY_UP)	/* it's a release event*/
-	    type = KeyRelease;
-	else
-	    type = KeyPress;
-
-    /* get an xEvent from some place where ProcessInputEvents can find it. */
-    /* I don't know how your implementation does this. */
-
-    xE = somehow_get_xEvent();
-
-    xE->u.u.type = type;
-    xE->u.u.detail = key_or_button_code;
-    xE->u.keyButtonPointer.time = GetTimeInMillis();
-    xE->u.keyButtonPointer.rootX = x;
-    xE->u.keyButtonPointer.rootY = y;
-
-    /* now call ProcessInputEvents to send the event to DIX for routing to the
-       appropriate client(s). */
-
-    ProcessInputEvents();
-    }
-
-
-XTestJumpPointer performs the equivalent function for pointer events.
-
-void
-XTestJumpPointer (x, y, dev_type)
-    int x,y;
-    int dev_type;
-    {
-    /* get an xEvent from some place where ProcessInputEvents can find it. */
-    /* I don't know how your implementation does this. */
-
-    xE = somehow_get_xEvent();
-
-    xE->u.u.type = MotionNotify;
-    xE->u.keyButtonPointer.time = GetTimeInMillis();
-    xE->u.keyButtonPointer.rootX = x;
-    xE->u.keyButtonPointer.rootY = y;
-
-    /* Call some place in your server code that takes care of acceleration and 
-       threshold.  Also constrain the move to the screen bounds.  You
-       may also have a motion history buffer that should be updated with
-       the information in this event.
-       */
-
-    deal_with_acceleration ();
-    constrainxy();
-    update_motion_history();
-
-    /* now call ProcessInputEvents to send the event to DIX for routing to the
-       appropriate client(s). */
-
-    ProcessInputEvents();
-    }
-
-XTestGetPointerPos returns the server's notion of where the X pointer currently
-is.  This is probably kept by ddx in some implementation-specific structure:
-
-Implementation_Specific_Struct *i;
-
-void
-XTestGetPointerPos (x,y)
-    short *x,*y;
-    {
-    *x = i->x;
-    *y = i->y;
-    }