diff options
Diffstat (limited to 'libX11/specs/libX11/CH01.xml')
-rw-r--r-- | libX11/specs/libX11/CH01.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/libX11/specs/libX11/CH01.xml b/libX11/specs/libX11/CH01.xml index 21750aba1..8d2092420 100644 --- a/libX11/specs/libX11/CH01.xml +++ b/libX11/specs/libX11/CH01.xml @@ -151,7 +151,7 @@ which will be called when the error is reported. <indexterm><primary>XSync</primary></indexterm> If a client does not want a request to execute asynchronously, it can follow the request with a call to -<function>XSync</function>, +<xref linkend='XSync' xrefstyle='select: title'/>, which blocks until all previously buffered asynchronous events have been sent and acted on. As an important side effect, @@ -206,12 +206,12 @@ programs must be prepared to handle (or ignore) events of all types. Input events (for example, a key pressed or the pointer moved) arrive asynchronously from the server and are queued until they are requested by an explicit call (for example, -<function>XNextEvent</function> +<xref linkend='XNextEvent' xrefstyle='select: title'/> or -<function>XWindowEvent</function>). +<xref linkend='XWindowEvent' xrefstyle='select: title'/>). In addition, some library functions (for example, -<function>XRaiseWindow</function>) +<xref linkend='XRaiseWindow' xrefstyle='select: title'/>) generate <symbol>Expose</symbol> and @@ -220,7 +220,7 @@ events. These events also arrive asynchronously, but the client may <indexterm><primary>XSync</primary></indexterm> wish to explicitly wait for them by calling -<function>XSync</function> +<xref linkend='XSync' xrefstyle='select: title'/> after calling a function that can cause the server to generate events. </para> </sect1> @@ -316,7 +316,7 @@ reference this file directly. <indexterm><primary>Headers</primary><secondary><X11/Xcms.h></secondary></indexterm> <para> This file contains symbols for much of the color management facilities -described in <link linkend="color_management_functions">chapter 6</link>. +described in <link linkend='Color_Management_Functions'>chapter 6</link>. All functions, types, and symbols with the prefix "Xcms", plus the Color Conversion Contexts macros, are declared in this file. <filename class="headerfile"><X11/Xlib.h></filename> @@ -334,8 +334,8 @@ must be included before including this file. This file declares various functions, types, and symbols used for inter-client communication and application utility functions, which are described in chapters -<link linkend="inter_client_communication_functions">14</link> and -<link linkend="application_utility_functions">16</link>. +<link linkend='Inter_Client_Communication_Functions'>14</link> and +<link linkend='Application_Utility_Functions'>16</link>. <filename class="headerfile"><X11/Xlib.h></filename> must be included before including this file. </para> </listitem> @@ -349,7 +349,7 @@ which are described in chapters <para> This file declares all functions, types, and symbols for the resource manager facilities, which are described in -<link linkend="resource_manager_functions">chapter 15</link>. +<link linkend='Resource_Manager_Functions'>chapter 15</link>. <filename class="headerfile"><X11/Xlib.h></filename> <!-- xref --> must be included before including this file. </para> @@ -683,7 +683,7 @@ rather than presume control of the entire screen. What you do inside of your top-level window, however, is up to your application. For further information, -see <link linkend="inter_client_communication_functions">chapter 14</link> +see <link linkend='Inter_Client_Communication_Functions'>chapter 14</link> and the <citetitle>Inter-Client Communication Conventions Manual</citetitle>. </para> </listitem> |