/usr/share/doc/libxtst-dev/xtestlib.html

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>XTEST Extension Library</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><style xmlns="" type="text/css">/*
 * Copyright (c) 2011 Gaetan Nadon
 * Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
 *
 * Permission is hereby granted, free of charge, to any person obtaining a
 * copy of this software and associated documentation files (the "Software"),
 * to deal in the Software without restriction, including without limitation
 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
 * and/or sell copies of the Software, and to permit persons to whom the
 * Software is furnished to do so, subject to the following conditions:
 *
 * The above copyright notice and this permission notice (including the next
 * paragraph) shall be included in all copies or substantial portions of the
 * Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
 * DEALINGS IN THE SOFTWARE.
 */

/*
 * Shared stylesheet for X.Org documentation translated to HTML format
 * http://www.sagehill.net/docbookxsl/UsingCSS.html
 * http://www.w3schools.com/css/default.asp
 * https://addons.mozilla.org/en-US/firefox/addon/web-developer/developers
 * https://addons.mozilla.org/en-US/firefox/addon/font-finder/
 */

/*
 * The sans-serif fonts are considered more legible on a computer screen
 * http://dry.sailingissues.com/linux-equivalents-verdana-arial.html
 *
 */
body {
  font-family: "Bitstream Vera Sans", "DejaVu Sans", Tahoma, Geneva, Arial, Sans-serif;
  /* In support of using "em" font size unit, the w3c recommended method */
  font-size: 100%;
}

/*
 * Selection: all elements requiring mono spaced fonts.
 *
 * The family names attempt to match the proportionally spaced font
 * family names such that the same font name is used for both.
 * We'd like to use Bitstream, for example, in both proportionally and
 * mono spaced font text.
 */
.command,
.errorcode,
.errorname,
.errortype,
.filename,
.funcsynopsis,
.function,
.parameter,
.programlisting,
.property,
.screen,
.structname,
.symbol,
.synopsis,
.type
{
  font-family:  "Bitstream Vera Sans Mono", "DejaVu Sans Mono", Courier, "Liberation Mono", Monospace;
}

/*
 * Books have a title page, a preface, some chapters and appendices,
 * a glossary, an index and a bibliography, in that order.
 *
 * An Article has no preface and no chapters. It has sections, appendices,
 * a glossary, an index and a bibliography.
 */

/*
 * Selection: book main title and subtitle
 */
div.book>div.titlepage h1.title,
div.book>div.titlepage h2.subtitle {
  text-align: center;
}

/*
 * Selection: article main title and subtitle
 */
div.article>div.titlepage h2.title,
div.article>div.titlepage h3.subtitle,
div.article>div.sect1>div.titlepage h2.title,
div.article>div.section>div.titlepage h2.title {
  text-align: center;
}

/*
 * Selection: various types of authors and collaborators, individuals or corporate
 *
 * These authors are not always contained inside an authorgroup.
 * They can be contained inside a lot of different parent types where they might
 * not be centered.
 * Reducing the margin at the bottom makes a visual separation between authors
 * We specify here the ones on the title page, others may be added based on merit.
 */
div.titlepage .authorgroup,
div.titlepage .author,
div.titlepage .collab,
div.titlepage .corpauthor,
div.titlepage .corpcredit,
div.titlepage .editor,
div.titlepage .othercredit {
  text-align: center;
  margin-bottom: 0.25em;
}

/*
 * Selection: the affiliation of various types of authors and collaborators,
 * individuals or corporate.
 */
div.titlepage .affiliation {
  text-align: center;
}

/*
 * Selection: product release information (X Version 11, Release 7)
 *
 * The releaseinfo element can be contained inside a lot of different parent
 * types where it might not be centered.
 * We specify here the one on the title page, others may be added based on merit.
 */
div.titlepage p.releaseinfo {
  font-weight: bold;
  text-align: center;
}

/*
 * Selection: publishing date
 */
div.titlepage .pubdate {
  text-align: center;
}

/*
 * The legal notices are displayed in smaller sized fonts
 * Justification is only supported in IE and therefore not requested.
 *
 */
.legalnotice {
  font-size: small;
  font-style: italic;
}

/*
 * Selection: book or article main ToC title
 * A paragraph is generated for the title rather than a level 2 heading.
 * We do not want to select chapters sub table of contents, only the main one
 */
div.book>div.toc>p,
div.article>div.toc>p {
  font-size: 1.5em;
  text-align: center;
}

/*
 * Selection: major sections of a book or an article
 *
 * Unlike books, articles do not have a titlepage element for appendix.
 * Using the selector "div.titlepage h2.title" would be too general.
 */
div.book>div.preface>div.titlepage h2.title,
div.book>div.chapter>div.titlepage h2.title,
div.article>div.sect1>div.titlepage h2.title,
div.article>div.section>div.titlepage h2.title,
div.book>div.appendix>div.titlepage h2.title,
div.article>div.appendix h2.title,
div.glossary>div.titlepage h2.title,
div.index>div.titlepage h2.title,
div.bibliography>div.titlepage h2.title {
   /* Add a border top over the major parts, just like printed books */
   /* The Gray color is already used for the ruler over the main ToC. */
  border-top-style: solid;
  border-top-width: 2px;
  border-top-color: Gray;
  /* Put some space between the border and the title */
  padding-top: 0.2em;
  text-align: center;
}

/*
 * A Screen is a verbatim environment for displaying text that the user might
 * see on a computer terminal. It is often used to display the results of a command.
 *
 * http://www.css3.info/preview/rounded-border/
 */
.screen {
  background: #e0ffff;
  border-width: 1px;
  border-style: solid;
  border-color: #B0C4DE;
  border-radius: 1.0em;
  /* Browser's vendor properties prior to CSS 3 */
  -moz-border-radius: 1.0em;
  -webkit-border-radius: 1.0em;
  -khtml-border-radius: 1.0em;
  margin-left: 1.0em;
  margin-right: 1.0em;
  padding: 0.5em;
}

/*
 * Emphasis program listings with a light shade of gray similar to what
 * DocBook XSL guide does: http://www.sagehill.net/docbookxsl/ProgramListings.html
 * Found many C API docs on the web using like shades of gray.
 */
.programlisting {
  background: #F4F4F4;
  border-width: 1px;
  border-style: solid;
  border-color: Gray;
  padding: 0.5em;
}

/*
 * Emphasis functions synopsis using a darker shade of gray.
 * Add a border such that it stands out more.
 * Set the padding so the text does not touch the border.
 */
.funcsynopsis, .synopsis {
  background: #e6e6fa;
  border-width: 1px;
  border-style: solid;
  border-color: Gray;
  clear: both;
  margin: 0.5em;
  padding: 0.25em;
}

/*
 * Selection: paragraphs inside synopsis
 *
 * Removes the default browser margin, let the container set the padding.
 * Paragraphs are not always used in synopsis
 */
.funcsynopsis p,
.synopsis p {
  margin: 0;
  padding: 0;
}

/*
 * Selection: variable lists, informal tables and tables
 *
 * Note the parameter name "variablelist.as.table" in xorg-xhtml.xsl
 * A table with rows and columns is constructed inside div.variablelist
 *
 * Set the left margin so it is indented to the right
 * Display informal tables with single line borders
 */
table {
  margin-left: 0.5em;
  border-collapse: collapse;
}

/*
 * Selection: paragraphs inside tables
 *
 * Removes the default browser margin, let the container set the padding.
 * Paragraphs are not always used in tables
 */
td p {
  margin: 0;
  padding: 0;
}

/*
 * Add some space between the left and right column.
 * The vertical alignment helps the reader associate a term
 * with a multi-line definition.
 */
td, th {
  padding-left: 1.0em;
  padding-right: 1.0em;
  vertical-align: top;
}

.warning {
  border: 1px solid red;
  background: #FFFF66;
  padding-left: 0.5em;
}
</style></head><body><div class="book"><div class="titlepage"><div><div><h1 class="title"><a id="xtestlib"></a>XTEST Extension Library</h1></div><div><h2 class="subtitle">X Consortium Standard</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Kieron</span> <span class="surname">Drake</span></h3><div class="affiliation"><span class="orgname">UniSoft Ltd.<br /></span></div></div></div></div><div><p class="releaseinfo">X Version 11, Release 7.6</p></div><div><p class="releaseinfo">Version 2.2</p></div><div><p class="copyright">Copyright © 1992 UniSoft Group Ltd.</p></div><div><div class="legalnotice"><a id="idp28503948"></a><p>
Permission to use, copy, modify, and distribute this documentation for
any purpose and without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.  UniSoft
makes no representations about the suitability for any purpose of the
information in this document.  This documentation is provided
“as is” without express or implied warranty.
</p></div></div><div><div class="legalnotice"><a id="idp27784036"></a><p class="multiLicensing">Copyright © 1992,1994 X Consortium</p><p>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files
(the “Software”), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following
conditions:
</p><p>
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
</p><p>
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN
NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
</p><p>
Except as contained in this notice, the name of the X Consortium shall not
be used in advertising or otherwise to promote the sale, use or other dealings
in this Software without prior written authorization from the X Consortium.
</p><p>X Window System is a trademark of The Open Group.</p></div></div></div><hr /></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#Overview">1. Overview</a></span></dt><dt><span class="chapter"><a href="#Description">2. Description</a></span></dt><dt><span class="chapter"><a href="#C_Language_Binding">3. C Language Binding</a></span></dt><dt><span class="chapter"><a href="#References">4. References</a></span></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="Overview"></a>Chapter 1. Overview</h1></div></div></div><p>
This extension is a minimal set of client and server extensions
required to completely test the X11 server with no user intervention.
</p><p>
This extension is not intended to support general journaling and
playback of user actions.  This is a difficult area [XTrap, 89] as it attempts
to synchronize synthetic user interactions with their effects; it is at the
higher level of dialogue recording/playback rather than at the strictly lexical
level.  We are interested only in the latter, simpler, case.  A more detailed
discussion and justification of the extension functionality is given in
[Drake, 91].
</p><p>
We are aiming only to provide a minimum set of facilities that
solve immediate testing and validation problems.  The testing extension
itself needs testing, where possible, and so should be as simple as possible.
</p><p>We have also tried to:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: bullet; "><li class="listitem" style="list-style-type: disc"><p>
Confine the extension to an appropriate high level
within the server to minimize portability problems.  In practice this
means that the extension should be at the DIX level or use the
DIX/DDX interface, or both.  This has effects, in particular, on the
level at which "input synthesis" can occur.
    </p></li><li class="listitem" style="list-style-type: disc"><p>
Minimize the changes required in the rest of the server.
    </p></li><li class="listitem" style="list-style-type: disc"><p>
Minimize performance penalties on normal server operation.
    </p></li></ul></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="Description"></a>Chapter 2. Description</h1></div></div></div><p>The functions provided by this extension fall into two groups:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Client Operations</p><p>
These routines manipulate otherwise hidden client-side behavior.
The actual implementation will depend on the details of the actual language
binding and what degree of request buffering, GContext caching, and so on, is
provided.  In the C binding, defined in section 7, routines are provided
to access the internals of two opaque data structures -
<span class="symbol">GC</span>s
and
<code class="function">Visual</code>s - and to discard any requests pending within the
output buffer of a connection.  The exact details can be expected to differ for
other language bindings.
      </p></li><li class="listitem"><p>Server Requests</p><p>
The first of these requests is similar to that provided in most
extensions: it allows a client to specify a major and minor version
number to the server and for the server to respond with major and minor
versions of its own.  The remaining two requests allow the following:
      </p></li><li class="listitem"><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
Access to an otherwise "write-only" server resource: the
cursor associated with a given window
          </p></li><li class="listitem"><p>
Perhaps most importantly, limited synthesis of input
device events, almost as if a cooperative user had moved the pointing device
or pressed a key or button.
          </p></li></ul></div></li></ul></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="C_Language_Binding"></a>Chapter 3. C Language Binding</h1></div></div></div><p>
The C functions either provide direct access to the protocol and add no
additional semantics to those defined in section 5 or they correspond
directly to the abstract descriptions of client operations in section 4.
</p><p>
All XTEST extension functions and procedures, and all manifest constants
and macros, will start with the string "XTest".  All operations are
classified as server/client (Server) or client-only (Client).
All routines that have return type Status will return nonzero for
"success" and zero for "failure."  Even if the XTEST extension is
supported, the server may withdraw such facilities arbitrarily; in which case
they will subsequently return zero.
</p><p>
The include file for this extension is
&lt;<span class="symbol">X11/extensions/XTest.h</span>&gt;.
</p><div class="funcsynopsis"><a id="XTestQueryExtension"></a><p><code class="funcdef">Bool<strong class="fsfunc"> XTestQueryExtension</strong>(</code>Display<var class="pdparam"> *display</var>, int<var class="pdparam"> *event_base</var>, int<var class="pdparam"> *error_base</var>, int<var class="pdparam"> *major_version</var>, int<var class="pdparam"> *minor_version</var><code>)</code>;</p></div><p>
<a class="xref" href="#XTestQueryExtension"><code class="function"> XTestQueryExtension</code></a>
returns
<code class="function">True</code>
if the specified display supports the XTEST extension, else
<code class="function">False</code>
If the extension is supported, *event_base would be set to the event number
for the first event for this extension and *error_base would be set to the
error number for the first error for this extension.  As no errors or
events are defined for this version of the extension, the values returned
here are not defined (nor useful).  If the extension is supported,
*major_version and *minor_version are set to the major and minor version
numbers of the extension supported by the display.  Otherwise, none of
the arguments are set.
</p><div class="funcsynopsis"><a id="XTestCompareCursorWithWindow"></a><p><code class="funcdef">Bool<strong class="fsfunc"> XTestCompareCursorWithWindow</strong>(</code>Display<var class="pdparam"> *display</var>, Window<var class="pdparam"> *window</var>, Cursor<var class="pdparam"> cursor</var><code>)</code>;</p></div><p>If the extension is supported,
<a class="xref" href="#XTestCompareCursorWithWindow"><code class="function"> XTestCompareCursorWithWindow</code></a>
performs a comparison of the cursor whose ID is specified by cursor (which
may be
<code class="function">None</code>
with the cursor of the window specified by window returning
<code class="function">True</code>
if they are the same and
<code class="function">False</code>
otherwise.  If the extension is not supported, then the request is ignored and
zero is returned.
</p><div class="funcsynopsis"><a id="XTestCompareCurrentCursorWithWindow"></a><p><code class="funcdef">Bool<strong class="fsfunc">XTestCompareCurrentCursorWithWindow</strong>(</code>Display<var class="pdparam"> *display</var>, Window<var class="pdparam"> window</var><code>)</code>;</p></div><p>If the extension is supported,
<a class="xref" href="#XTestCompareCurrentCursorWithWindow"><code class="function">XTestCompareCurrentCursorWithWindow</code></a>
performs a comparison of the current cursor with the cursor of the specified
window returning
<code class="function">True</code>
if they are the same and
<code class="function">False</code>
otherwise.  If the extension is not supported, then the request is ignored and
zero is returned.
</p><div class="funcsynopsis"><a id="XTestFakeKeyEvent"></a><p><code class="funcdef"><strong class="fsfunc">XTestFakeKeyEvent</strong>(</code>Display<var class="pdparam"> *display</var>, unsigned int<var class="pdparam"> keycode</var>, Bool<var class="pdparam"> is_press</var>, unsigned long<var class="pdparam"> delay</var><code>)</code>;</p></div><p>If the extension is supported,
<a class="xref" href="#XTestFakeKeyEvent"><code class="function">XTestFakeKeyEvent</code></a>
requests the server to simulate either a
<code class="function">KeyPress</code>
(if is_press is
<code class="function">True</code>
or a
<code class="function">KeyRelease</code>
(if is_press is
<code class="function">False</code>
of the key with the specified keycode; otherwise, the request is ignored.
</p><p>
If the extension is supported, the simulated event will not be processed
until delay milliseconds after the request is received (if delay is
<code class="function">CurrentTime</code>
then this is interpreted as no delay at all).  No other requests from
this client will be processed until this delay, if any, has expired
and subsequent processing of the simulated event has been completed.
</p><div class="funcsynopsis"><a id="XTestFakeButtonEvent"></a><p><code class="funcdef"><strong class="fsfunc">XTestFakeButtonEvent</strong>(</code>Display<var class="pdparam"> *display</var>, unsigned int<var class="pdparam"> button</var>, Bool<var class="pdparam"> is_press</var>, unsigned long<var class="pdparam"> delay</var><code>)</code>;</p></div><p>If the extension is supported,
<a class="xref" href="#XTestFakeButtonEvent"><code class="function">XTestFakeButtonEvent</code></a>
requests the server to simulate either a
<code class="function">ButtonPress</code>
(if is_press is
<code class="function">True</code>
or a
<code class="function">ButtonRelease</code>
(if is_press is
<code class="function">False</code>
of the logical button numbered by the specified button; otherwise, the
request is ignored.
</p><p>If the extension is supported,
the simulated event will not be processed until delay milliseconds
after the request is received (if delay is
<code class="function">CurrentTime</code>
then this is interpreted as no delay at all).  No other requests from
this client will be processed until this delay, if any, has expired
and subsequent processing of the simulated event has been completed.
</p><div class="funcsynopsis"><a id="XTestFakeMotionEvent"></a><p><code class="funcdef"><strong class="fsfunc">XTestFakeMotionEvent</strong>(</code>Display<var class="pdparam"> *display</var>, int<var class="pdparam"> screen_number</var>, int<var class="pdparam"> x</var>, int<var class="pdparam"> y</var>, unsigned long<var class="pdparam"> delay</var><code>)</code>;</p></div><p>If the extension is supported,
<a class="xref" href="#XTestFakeMotionEvent"><code class="function">XTestFakeMotionEvent</code></a>
requests the server to simulate a movement of the pointer to the specified
position (x, y) on the root window of screen_number; otherwise, the request
is ignored.  If screen_number is -1, the current screen (that the pointer
is on) is used.
</p><p>
If the extension is supported, the simulated event will not be processed
until delay milliseconds after the request is received (if delay is
<code class="function">CurrentTime</code>
then this is interpreted as no delay at all).  No other requests from
this client will be processed until this delay, if any, has expired
and subsequent processing of the simulated event has been completed.
</p><div class="funcsynopsis"><a id="XTestFakeRelativeMotionEvent"></a><p><code class="funcdef"><strong class="fsfunc">XTestFakeRelativeMotionEvent</strong>(</code>Display<var class="pdparam"> *display</var>, int<var class="pdparam"> screen_number</var>, int<var class="pdparam"> x</var>, int<var class="pdparam"> y</var>, unsigned long<var class="pdparam"> delay</var><code>)</code>;</p></div><p>
If the extension is supported,
<a class="xref" href="#XTestFakeRelativeMotionEvent"><code class="function">XTestFakeRelativeMotionEvent</code></a>
requests the server to simulate a movement of the pointer by the specified
offsets (x, y) relative to the current pointer position on screen_number;
otherwise, the request is ignored.  If screen_number is -1, the
current screen (that the pointer is on) is used.
</p><p>
If the extension is supported, the simulated event will not be processed
until delay milliseconds after the request is received (if delay is
<code class="function">CurrentTime</code>
then this is interpreted as no delay at all).  No other requests from
this client will be processed until this delay, if any, has expired
and subsequent processing of the simulated event has been completed.
</p><div class="funcsynopsis"><a id="XTestGrabControl"></a><p><code class="funcdef"><strong class="fsfunc">XTestGrabControl</strong>(</code>Display<var class="pdparam"> *display</var>, Bool<var class="pdparam"> impervious</var><code>)</code>;</p></div><p>If impervious is
<code class="function">True</code>
then the executing client becomes impervious to server grabs.  If impervious is
<code class="function">False</code>
then the executing client returns to the normal state of being susceptible
to server grabs.
</p><div class="funcsynopsis"><a id="XTestSetGContextOfGC"></a><p><code class="funcdef">Bool<strong class="fsfunc"> XTestSetGContextOfGC</strong>(</code>GC<var class="pdparam"> gc</var>, GContext<var class="pdparam"> gid</var><code>)</code>;</p></div><p>
<a class="xref" href="#XTestSetGContextOfGC"><code class="function"> XTestSetGContextOfGC</code></a>
sets the GContext within the opaque datatype referenced by gc to
be that specified by gid.
</p><div class="funcsynopsis"><a id="XTestSetVisualIDOfVisual"></a><p><code class="funcdef"><strong class="fsfunc">XTestSetVisualIDOfVisual</strong>(</code>Visual<var class="pdparam"> *visual</var>, VisualID<var class="pdparam"> visualid</var><code>)</code>;</p></div><p>
<a class="xref" href="#XTestSetVisualIDOfVisual"><code class="function">XTestSetVisualIDOfVisual</code></a>
sets the VisualID within the opaque datatype referenced by visual to
be that specified by visualid.
</p><div class="funcsynopsis"><a id="XTestDiscard"></a><p><code class="funcdef">Bool<strong class="fsfunc"> XTestDiscard</strong>(</code>Display<var class="pdparam"> *display</var><code>)</code>;</p></div><p>
<a class="xref" href="#XTestDiscard"><code class="function"> XTestDiscard</code></a>
discards any requests within the output buffer for the specified display.
It returns
<code class="function">True</code>
if any requests were discarded; otherwise, it returns
<code class="function">False</code>
</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="References"></a>Chapter 4. References</h1></div></div></div><p>
Annicchiarico, D., et al., <span class="emphasis"><em>XTrap: The XTrap
Architecture</em></span>.
Digital Equipment Corporation, July 1991.
</p><p>
Drake, K. J., <span class="emphasis"><em>Some Proposals for a Minimum X11
Testing Extension</em></span>.
UniSoft Ltd., June 1991.
</p></div></div></body></html>
libxtst-doc 2:1.2.2-1 / usr / share / doc / libxtst-dev / xtestlib.html
