summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Dew <marcoz@osource.org>2011-10-21 22:54:27 -0600
committerMatt Dew <marcoz@osource.org>2011-10-21 22:54:27 -0600
commit388af5f79aa28bcd1c053fb2e669d0ac31e90ef0 (patch)
tree729ae021b07beeaaa4684b73c4dae51feb41d6c8
parent6b4bcb3177919183bb6feb43054e6d85537d0e34 (diff)
updated CH07.xml
Diffstat
-rw-r--r--specs/CH07.xml3244
1 files changed, 1195 insertions, 2049 deletions
diff --git a/specs/CH07.xml b/specs/CH07.xml
index 2e99ff2..53b35c4 100644
--- a/specs/CH07.xml
+++ b/specs/CH07.xml
@@ -1,77 +1,22 @@
-<!-- .\" $Xorg: CH07,v 1.4 2000/08/17 19:42:45 cpqbld Exp $ -->
-<!-- .\" Copyright \(co 1985, 1986, 1987, 1988, 1991, 1994 -->
-<!-- .\" X Consortium -->
-<!-- .\" -->
-<!-- .\" 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 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 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. -->
-<!-- .\" -->
-<!-- .\" 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. -->
-<!-- .\" -->
-<!-- .\" Copyright \(co 1985, 1986, 1987, 1988, 1991, 1994 -->
-<!-- .\" Digital Equipment Corporation, Maynard, Massachusetts. -->
-<!-- .\" -->
-<!-- .\" Permission to use, copy, modify and distribute this documentation for any -->
-<!-- .\" purpose and without fee is hereby granted, provided that the above copyright -->
-<!-- .\" notice appears in all copies and that both that copyright notice and this -->
-<!-- .\" permission notice appear in supporting documentation, and that the name of -->
-<!-- .\" Digital not be used in in advertising or publicity pertaining -->
-<!-- .\" to distribution of the software without specific, written prior permission. -->
-<!-- .\" Digital makes no representations about the suitability of the -->
-<!-- .\" software described herein for any purpose. -->
-<!-- .\" It is provided ``as is'' without express or implied warranty. -->
-<!-- .\" -->
-\&
-<!-- .sp 1 -->
-<!-- .ce 3 -->
-\s+1<function>Chapter 7</function>\s-1
-
-\s+1<function>Event Management</function>\s-1
-<!-- .sp 2 -->
-<!-- .nr H1 7 -->
-<!-- .nr H2 0 -->
-<!-- .nr H3 0 -->
-<!-- .nr H4 0 -->
-<!-- .nr H5 0 -->
-<para>
-<!-- .LP -->
-<!-- .XS -->
-<!-- Chapter 7 \(em Event Management -->
-<!-- .XE -->
+<chapter id='Event_Management'>
+<title>Event Management</title>
+<para>
While Xlib allows the reading and processing of events anywhere in an application,
widgets in the (tk neither directly read events
nor grab the server or pointer.
Widgets register procedures that are to be called
when an event or class of events occurs in that widget.
</para>
+
<para>
-<!-- .LP -->
A typical application consists of startup code followed by an event loop
that reads events and dispatches them by calling
the procedures that widgets have registered.
-The default event loop provided by the (xI is
-<function>XtAppMainLoop .</function>
+The default event loop provided by the Intrinsics is
+<function>XtAppMainLoop</function>.
</para>
+
<para>
-<!-- .LP -->
The event manager is a collection of functions to perform the following tasks:
</para>
<itemizedlist>
@@ -111,7 +56,7 @@ Register procedures to be called when specific events arrive.
</listitem>
<listitem>
<para>
-Register procedures to be called when the (xI will block.
+Register procedures to be called when the Intrinsics will block.
</para>
</listitem>
<listitem>
@@ -121,65 +66,47 @@ Enable safe operation in a multi-threaded environment.
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
Most widgets do not need to call any of the event handler functions explicitly.
The normal interface to X events is through the higher-level
translation manager,
which maps sequences of X events, with modifiers, into procedure calls.
Applications rarely use any of the event manager routines besides
-<function>XtAppMainLoop .</function>
-
+<function>XtAppMainLoop</function>.
</para>
-<sect2 id="Adding_and_Deleting_Additional_Event_Sources">
+<sect1 id="Adding_and_Deleting_Additional_Event_Sources">
<title>Adding and Deleting Additional Event Sources</title>
-<!-- .XS -->
-<!-- <function>(SN Adding and Deleting Additional Event Sources</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
While most applications are driven only by X events,
some applications need to incorporate other sources of input
-into the (xI event-handling mechanism.
+into the Intrinsics event-handling mechanism.
The event manager provides routines to integrate notification of timer events
and file data pending into this mechanism.
</para>
+
<para>
-<!-- .LP -->
The next section describes functions that provide input gathering from files.
-The application registers the files with the (xI read routine.
+The application registers the files with the Intrinsics read routine.
When input is pending on one of the files,
the registered callback procedures are invoked.
-
</para>
-<sect3 id="Adding_and_Removing_Input_Sources">
+<sect2 id="Adding_and_Removing_Input_Sources">
<title>Adding and Removing Input Sources</title>
-<!-- .XS -->
-<!-- <function>(SN Adding and Removing Input Sources</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To register a new file as an input source for a given application context, use
-<function>XtAppAddInput .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppAddInput" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-XtInputId XtAppAddInput(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>source</emphasis>, <emphasis remap='I'>condition</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>source</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>condition</emphasis>;
-<!-- .br -->
- XtInputCallbackProc <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAppAddInput</function>.
+</para>
+
+<funcsynopsis id='XtAppAddInput'>
+<funcprototype>
+<funcdef>XtInputId <function>XtAppAddInput</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>int <parameter>source</parameter></paramdef>
+ <paramdef>XtPointer <parameter>condition</parameter></paramdef>
+ <paramdef>XtInputCallbackProc <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -236,11 +163,9 @@ when it is called.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppAddInput</function>
-function registers with the (xI read routine a new source of events,
+function registers with the Intrinsics read routine a new source of events,
which is usually file input but can also be file output.
Note that <emphasis remap='I'>file</emphasis> should be loosely interpreted to mean any sink
or source of data.
@@ -249,39 +174,36 @@ also specifies the conditions under which the source can generate events.
When an event is pending on this source,
the callback procedure is called.
</para>
+
<para>
-<!-- .LP -->
The legal values for the <emphasis remap='I'>condition</emphasis> argument are operating-system-dependent.
On a POSIX-based system,
<emphasis remap='I'>source</emphasis> is a file number and the condition is some union of the following:
-<!-- .IN "XtInputReadMask" "" "@DEF@" -->
<variablelist>
<varlistentry>
<term>
- \fBXtInputReadMask\fR
+ <emphasis role='bold'>XtInputReadMask</emphasis>
</term>
<listitem>
<para>
Specifies that <emphasis remap='I'>proc</emphasis> is to be called when <emphasis remap='I'>source</emphasis> has data to be read.
-<!-- .IN "XtInputWriteMask" "" "@DEF@" -->
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
- \fBXtInputWriteMask\fR
+ <emphasis role='bold'>XtInputWriteMask</emphasis>
</term>
<listitem>
<para>
Specifies that <emphasis remap='I'>proc</emphasis> is to be called when <emphasis remap='I'>source</emphasis> is ready
for writing.
-<!-- .IN "XtInputExceptMask" "" "@DEF@" -->
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
- \fBXtInputExceptMask\fR
+ <emphasis role='bold'>XtInputExceptMask</emphasis>
</term>
<listitem>
<para>
@@ -292,26 +214,22 @@ exception data.
</varlistentry>
</variablelist>
</para>
+
<para>
-<!-- .LP -->
Callback procedure pointers used to handle file events are of
type
-<function>XtInputCallbackProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtInputCallbackProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef void (*XtInputCallbackProc)(XtPointer, int*, XtInputId*);
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- int *<emphasis remap='I'>source</emphasis>;
-<!-- .br -->
- XtInputId *<emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+<function>XtInputCallbackProc</function>.
+</para>
+
+<funcsynopsis id='XtInputCallbackProc'>
+<funcprototype>
+<funcdef>void <function>*XtInputCallbackProc</function></funcdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>int *<parameter>source</parameter></paramdef>
+ <paramdef>XtInputId *<parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -320,7 +238,7 @@ typedef void (*XtInputCallbackProc)(XtPointer, int*, XtInputId*);
<listitem>
<para>
Passes the client data argument that was registered for this procedure in
-<function>XtApp\%AddInput .</function>
+<function>XtApp\%AddInput</function>.
</para>
</listitem>
</varlistentry>
@@ -348,28 +266,23 @@ call.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
See Section 7.12 for information regarding the use of
<function>XtAppAddInput</function>
in multiple threads.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To discontinue a source of input, use
-<function>XtRemoveInput .</function>
+<function>XtRemoveInput</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveInput" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveInput(<emphasis remap='I'>id</emphasis>)
-<!-- .br -->
- XtInputId <emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRemoveInput'>
+<funcprototype>
+<funcdef>void <function>XtRemoveInput</function></funcdef>
+ <paramdef>XtInputId <parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -385,54 +298,42 @@ call.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveInput</function>
-function causes the (xI read routine to stop watching for events
+function causes the Intrinsics read routine to stop watching for events
from the file source specified by <emphasis remap='I'>id</emphasis>.
</para>
+
<para>
-<!-- .LP -->
See Section 7.12 for information regarding the use of
<function>XtRemoveInput</function>
in multiple threads.
-
</para>
-</sect3>
-<sect3 id="Adding_and_Removing_Blocking_Notifications">
+</sect2>
+
+<sect2 id="Adding_and_Removing_Blocking_Notifications">
<title>Adding and Removing Blocking Notifications</title>
-<!-- .XS -->
-<!-- <function>(SN Adding and Removing Blocking Notifications</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Occasionally it is desirable for an application to receive notification
-when the (xI event manager detects no pending input from file sources
+when the Intrinsics event manager detects no pending input from file sources
and no pending input from X server event sources and is about to block
in an operating system call.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To register a hook that is called immediately prior to event blocking, use
-<function>XtAppAddBlockHook .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppAddBlockHook" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-XtBlockHookId XtAppAddBlockHook(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>proc</emphasis>, \
-<emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- XtBlockHookProc <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAppAddBlockHook</function>.
+</para>
+
+<funcsynopsis id='XtAppAddBlockHook'>
+<funcprototype>
+<funcdef>XtBlockHookId <function>XtAppAddBlockHook</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>XtBlockHookProc <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -466,30 +367,26 @@ Specifies an argument passed to the specified procedure when it is called.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppAddBlockHook</function>
function registers the specified procedure and returns an identifier for it.
The hook procedure <emphasis remap='I'>proc</emphasis> is called at any time in the future when
-the (xI are about to block pending some input.
+the Intrinsics are about to block pending some input.
</para>
+
<para>
-<!-- .LP -->
The procedure pointers used to provide notification of event blocking
are of type
-<function>XtBlockHookProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtBlockHookProc" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtBlockHookProc</function>.
</para>
-<!-- .FD 0 -->
-typedef void (*XtBlockHookProc)(XtPointer);
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtBlockHookProc'>
+<funcprototype>
+<funcdef>void <function>*XtBlockHookProc</function></funcdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -498,27 +395,23 @@ typedef void (*XtBlockHookProc)(XtPointer);
<listitem>
<para>
Passes the client data argument that was registered for this procedure in
-<function>XtApp\%AddBlockHook .</function>
+<function>XtApp\%AddBlockHook</function>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
To discontinue the use of a procedure for blocking notification, use
-<function>XtRemoveBlockHook .</function>
+<function>XtRemoveBlockHook</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveBlockHook" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveBlockHook(<emphasis remap='I'>id</emphasis>)
-<!-- .br -->
- XtBlockHookId <emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRemoveBlockHook'>
+<funcprototype>
+<funcdef>void <function>XtRemoveBlockHook</function></funcdef>
+ <paramdef>XtBlockHookId <parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -527,55 +420,42 @@ void XtRemoveBlockHook(<emphasis remap='I'>id</emphasis>)
<listitem>
<para>
Specifies the identifier returned from the corresponding call to
-<function>XtAppAddBlockHook .</function>
+<function>XtAppAddBlockHook</function>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveBlockHook</function>
function removes the specified procedure from the list of procedures
-that are called by the (xI read routine before blocking on event sources.
-
+that are called by the Intrinsics read routine before blocking on event sources.
</para>
-</sect3>
-<sect3 id="Adding_and_Removing_Timeouts">
+</sect2>
+
+<sect2 id="Adding_and_Removing_Timeouts">
<title>Adding and Removing Timeouts</title>
-<!-- .XS -->
-<!-- <function>(SN Adding and Removing Timeouts</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
The timeout facility notifies the application or the widget
through a callback procedure that a specified time interval has elapsed.
Timeout values are uniquely identified by an interval id.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To register a timeout callback, use
-<function>XtAppAddTimeOut .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppAddTimeOut" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-XtIntervalId XtAppAddTimeOut(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>interval</emphasis>, <emphasis remap='I'>proc</emphasis>, \
-<emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- unsigned long <emphasis remap='I'>interval</emphasis>;
-<!-- .br -->
- XtTimerCallbackProc <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAppAddTimeOut</function>.
+</para>
+
+<funcsynopsis id='XtAppAddTimeOut'>
+<funcprototype>
+<funcdef>XtIntervalId <function>XtAppAddTimeOut</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>unsigned long <parameter>interval</parameter></paramdef>
+ <paramdef>XtTimerCallbackProc <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -620,8 +500,6 @@ when it is called.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppAddTimeOut</function>
function creates a timeout and returns an identifier for it.
@@ -633,24 +511,21 @@ or
is next called after the time interval elapses,
and then the timeout is removed.
</para>
+
<para>
-<!-- .LP -->
Callback procedure pointers used with timeouts are of
type
-<function>XtTimerCallbackProc .</function>
+<function>XtTimerCallbackProc</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtTimerCallbackProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef void (*XtTimerCallbackProc)(XtPointer, XtIntervalId*);
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- XtIntervalId *<emphasis remap='I'>timer</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtTimerCallbackProc'>
+<funcprototype>
+<funcdef>void <function>*XtTimerCallbackProc</function></funcdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>XtIntervalId *<parameter>timer</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -659,7 +534,7 @@ typedef void (*XtTimerCallbackProc)(XtPointer, XtIntervalId*);
<listitem>
<para>
Passes the client data argument that was registered for this procedure in
-<function>XtApp\%AddTimeOut .</function>
+<function>XtApp\%AddTimeOut</function>.
</para>
</listitem>
</varlistentry>
@@ -677,28 +552,23 @@ call.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
See Section 7.12 for information regarding the use of
<function>XtAppAddTimeOut</function>
in multiple threads.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To clear a timeout value, use
-<function>XtRemoveTimeOut .</function>
+<function>XtRemoveTimeOut</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveTimeOut" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveTimeOut(<emphasis remap='I'>timer</emphasis>)
-<!-- .br -->
- XtIntervalId <emphasis remap='I'>timer</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRemoveTimeOut'>
+<funcprototype>
+<funcdef>void <function>XtRemoveTimeOut</function></funcdef>
+ <paramdef>XtIntervalId <parameter>timer</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -712,60 +582,49 @@ Specifies the id for the timeout request to be cleared.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveTimeOut</function>
function removes the pending timeout.
Note that timeouts are automatically removed once they trigger.
</para>
+
<para>
-<!-- .LP -->
Please refer to Section 7.12 for information regarding the use of
<function>XtRemoveTimeOut</function>
in multiple threads.
-
</para>
-</sect3>
-<sect3 id="Adding_and_Removing_Signal_Callbacks">
+</sect2>
+
+<sect2 id="Adding_and_Removing_Signal_Callbacks">
<title>Adding and Removing Signal Callbacks</title>
-<!-- .XS -->
-<!-- <function>(SN Adding and Removing Signal Callbacks</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
The signal facility notifies the application or the widget through a
callback procedure that a signal or other external asynchronous event
has occurred. The registered callback procedures are uniquely identified
by a signal id.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
Prior to establishing a signal handler, the application or widget should
call
<function>XtAppAddSignal</function>
and store the resulting identifier in a place accessible to the signal
handler. When a signal arrives, the signal handler should call
<function>XtNoticeSignal</function>
-to notify the (xI that a signal has occured. To register a signal
+to notify the Intrinsics that a signal has occured. To register a signal
callback use
-<function>XtAppAddSignal .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppAddSignal" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-XtSignalId XtAppAddSignal(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- XtSignalCallbackProc <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAppAddSignal</function>.
+</para>
+
+<funcsynopsis id='XtAppAddSignal'>
+<funcprototype>
+<funcdef>XtSignalId <function>XtAppAddSignal</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>XtSignalCallbackProc <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -799,23 +658,18 @@ Specifies an argument passed to the specified procedure when it is called.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The callback procedure pointers used to handle signal events are of type
-<function>XtSignalCallbackProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtSignalCallbackProc" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtSignalCallbackProc</function>.
</para>
-<!-- .FD 0 -->
-typedef void (*XtSignalCallbackProc)(XtPointer, XtSignalId*);
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- XtSignalId *<emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtSignalCallbackProc'>
+<funcprototype>
+<funcdef>void <function>*XtSignalCallbackProc</function></funcdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>XtSignalId *<parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -824,7 +678,7 @@ typedef void (*XtSignalCallbackProc)(XtPointer, XtSignalId*);
<listitem>
<para>
Passes the client data argument that was registered for this procedure in
-<function>XtAppAddSignal .</function>
+<function>XtAppAddSignal</function>.
</para>
</listitem>
</varlistentry>
@@ -842,22 +696,17 @@ call.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
-To notify the (xI that a signal has occured, use
-<function>XtNoticeSignal .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtNoticeSignal" "" "@DEF@" -->
-<!-- .sp -->
-<!-- .sM -->
+To notify the Intrinsics that a signal has occured, use
+<function>XtNoticeSignal</function>.
</para>
-<!-- .FD 0 -->
-void XtNoticeSignal(<emphasis remap='I'>id</emphasis>)
-<!-- .br -->
- XtSignalId <emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtNoticeSignal'>
+<funcprototype>
+<funcdef>void <function>XtNoticeSignal</function></funcdef>
+ <paramdef>XtSignalId <parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -873,66 +722,62 @@ call.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
On a POSIX-based system,
<function>XtNoticeSignal</function>
-is the only (xI function that can safely be called from a signal handler.
+is the only Intrinsics function that can safely be called from a signal handler.
If
<function>XtNoticeSignal</function>
-is invoked multiple times before the (xI are able to invoke the
+is invoked multiple times before the Intrinsics are able to invoke the
registered callback, the callback is only called once.
-Logically, the (xI maintain ``pending'' flag for each registered callback.
+Logically, the Intrinsics maintain ``pending'' flag for each registered callback.
This flag is initially
<function>False</function>
and is set to
<function>True</function>
by
-<function>XtNoticeSignal .</function>
+<function>XtNoticeSignal</function>.
When
<function>XtAppNextEvent</function>
or
<function>XtAppProcessEvent</function>
(with a mask including
-<function>XtIMSignal )</function>
+<function>XtIMSignal</function>)
is called, all registered callbacks with ``pending''
<function>True</function>
are invoked and the flags are reset to
-<function>False .</function>
+<function>False</function>.
</para>
+
<para>
-<!-- .LP -->
If the signal handler wants to track how many times the signal has been
raised, it can keep its own private counter. Typically the handler would
not do any other work; the callback does the actual processing for the
-signal. The (xI never block signals from being raised, so if a given
-signal can be raised multiple times before the (xI can invoke the
+signal. The Intrinsics never block signals from being raised, so if a given
+signal can be raised multiple times before the Intrinsics can invoke the
callback for that signal, the callback must be designed to deal with
-this. In another case, a signal might be raised just after the (xI
+this. In another case, a signal might be raised just after the Intrinsics
sets the pending flag to
<function>False</function>
but before the callback can get control, in which case the pending flag
will still be
<function>True</function>
-after the callback returns, and the (xI will invoke the callback
+after the callback returns, and the Intrinsics will invoke the callback
again, even though all of the signal raises have been handled. The
callback must also be prepared to handle this case.
</para>
+
<para>
-<!-- .LP -->
To remove a registered signal callback, call
-<function>XtRemoveSignal .</function>
+<function>XtRemoveSignal</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveSignal" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveSignal(<emphasis remap='I'>id</emphasis>)
-<!-- .br -->
- XtSignalId <emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRemoveSignal'>
+<funcprototype>
+<funcdef>void <function>XtRemoveSignal</function></funcdef>
+ <paramdef>XtSignalId <parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -941,16 +786,14 @@ void XtRemoveSignal(<emphasis remap='I'>id</emphasis>)
<listitem>
<para>
Specifies the id returned by the corresponding call to
-<function>XtAppAddSignal .</function>
+<function>XtAppAddSignal</function>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The client should typically disable the source of the signal before calling
-<function>XtRemoveSignal .</function>
+<function>XtRemoveSignal</function>.
If the signal could have been raised again before the source was disabled
and the client wants to process it, then after disabling the source but
before calling
@@ -960,56 +803,50 @@ the client can test for signals with
and process them by calling
<function>XtAppProcessEvent</function>
with the mask
-<function>XtIMSignal .</function>
-
+<function>XtIMSignal</function>.
</para>
-</sect3>
</sect2>
-<sect2 id="Constraining_Events_to_a_Cascade_of_Widgets">
+</sect1>
+
+<sect1 id="Constraining_Events_to_a_Cascade_of_Widgets">
<title>Constraining Events to a Cascade of Widgets</title>
-<!-- .XS -->
-<!-- <function>(SN Constraining Events to a Cascade of Widgets</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-<!-- .IN "Grabbing Input" -->
-<!-- .IN "Input Grabbing" -->
Modal widgets are widgets that, except for the input directed to them,
lock out user input to the application.
</para>
+
<para>
-<!-- .LP -->
When a modal menu or modal dialog box is popped up using
-<function>XtPopup ,</function>
+<function>XtPopup</function>,
user events (keyboard and pointer events) that occur outside the modal
widget should be delivered to the modal widget or ignored.
In no case will user events be delivered to a widget outside
the modal widget.
</para>
+
<para>
-<!-- .LP -->
Menus can pop up submenus, and dialog boxes can pop up further dialog
boxes to create a pop-up cascade.
In this case,
user events may be delivered to one of several modal widgets in the cascade.
</para>
+
<para>
-<!-- .LP -->
Display-related events should be delivered outside the modal cascade so that
exposure events and the like keep the application's display up-to-date.
Any event that occurs within the cascade is delivered as usual.
The user events delivered to the most recent spring-loaded shell
in the cascade when they occur outside the cascade are called remap events
and are
-<function>KeyPress ,</function>
-<function>KeyRelease ,</function>
-<function>ButtonPress ,</function>
+<function>KeyPress</function>,
+<function>KeyRelease</function>,
+<function>ButtonPress</function>,
and
-<function>ButtonRelease .</function>
+<function>ButtonRelease</function>.
The user events ignored when they occur outside the cascade are
<function>MotionNotify</function>
and
-<function>EnterNotify .</function>
+<function>EnterNotify</function>.
All other events are delivered normally.
In particular, note that this is one
way in which widgets can receive
@@ -1021,8 +858,8 @@ this, typically by ignoring any unmatched
<function>LeaveNotify</function>
events.
</para>
+
<para>
-<!-- .LP -->
<function>XtPopup</function>
uses the
<function>XtAddGrab</function>
@@ -1030,28 +867,22 @@ and
<function>XtRemoveGrab</function>
functions to constrain user events to a modal cascade
and subsequently to remove a grab when the modal widget is popped down.
-
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To constrain or redirect user input to a modal widget, use
-<function>XtAddGrab .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAddGrab" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAddGrab(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>exclusive</emphasis>, <emphasis remap='I'>spring_loaded</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>exclusive</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>spring_loaded</emphasis>;
-<!-- .FN -->
+<function>XtAddGrab</function>.
+</para>
+
+<funcsynopsis id='XtAddGrab'>
+<funcprototype>
+<funcdef>void <function>XtAddGrab</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>Boolean <parameter>exclusive</parameter></paramdef>
+ <paramdef>Boolean <parameter>spring_loaded</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1059,7 +890,7 @@ void XtAddGrab(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>exclusive</
</term>
<listitem>
<para>
-Specifies the widget to add to the modal cascade. (cI
+Specifies the widget to add to the modal cascade. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -1087,21 +918,19 @@ a pointer button.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAddGrab</function>
function appends the widget to the modal cascade
and checks that <emphasis remap='I'>exclusive</emphasis> is
<function>True</function>
if <emphasis remap='I'>spring_loaded</emphasis> is
-<function>True .</function>
+<function>True</function>.
If this condition is not met,
<function>XtAddGrab</function>
generates a warning message.
</para>
+
<para>
-<!-- .LP -->
The modal cascade is used by
<function>XtDispatchEvent</function>
when it tries to dispatch a user event.
@@ -1110,54 +939,51 @@ When at least one modal widget is in the widget cascade,
first determines if the event should be delivered.
It starts at the most recent cascade entry and follows the cascade up to and
including the most recent cascade entry added with the <emphasis remap='I'>exclusive</emphasis> parameter
-<function>True .</function>
+<function>True</function>.
</para>
+
<para>
-<!-- .LP -->
This subset of the modal cascade along with all descendants of these widgets
comprise the active subset.
User events that occur outside the widgets in this subset are ignored
or remapped.
Modal menus with submenus generally add a submenu widget to the cascade
with <emphasis remap='I'>exclusive</emphasis>
-<function>False .</function>
+<function>False</function>.
Modal dialog boxes that need to restrict user input to the most deeply nested
dialog box add a subdialog widget to the cascade with <emphasis remap='I'>exclusive</emphasis>
-<function>True .</function>
+<function>True</function>.
User events that occur within the active subset are delivered to the
appropriate widget, which is usually a child or further descendant of the modal
widget.
</para>
+
<para>
-<!-- .LP -->
Regardless of where in the application they occur,
remap events are always delivered to the most recent widget in the active
subset of the cascade registered with <emphasis remap='I'>spring_loaded</emphasis>
-<function>True ,</function>
+<function>True</function>,
if any such widget exists.
If the event
occurred in the active subset of the cascade but outside the
spring-loaded widget, it is delivered normally before being
delivered also to the spring-loaded widget.
-Regardless of where it is dispatched, the (xI do not modify
+Regardless of where it is dispatched, the Intrinsics do not modify
the contents of the event.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To remove the redirection of user input to a modal widget, use
-<function>XtRemoveGrab .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveGrab" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtRemoveGrab</function>.
</para>
-<!-- .FD 0 -->
-void XtRemoveGrab(<emphasis remap='I'>w</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRemoveGrab'>
+<funcprototype>
+<funcdef>void <function>XtRemoveGrab</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1171,55 +997,40 @@ Specifies the widget to remove from the modal cascade.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveGrab</function>
function removes widgets from the modal cascade starting
at the most recent widget up to and including the specified widget.
It issues a warning if the specified widget is not on the modal cascade.
-
</para>
-<sect3 id="Requesting_Key_and_Button_Grabs">
+<sect2 id="Requesting_Key_and_Button_Grabs">
<title>Requesting Key and Button Grabs</title>
-<!-- .XS -->
-<!-- <function>(SN Requesting Key and Button Grabs</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-The (xI provide a set of key and button grab interfaces that
-are parallel to those provided by Xlib and that allow the (xI
+The Intrinsics provide a set of key and button grab interfaces that
+are parallel to those provided by Xlib and that allow the Intrinsics
to modify event dispatching when necessary. (tk applications and
widgets that need to passively grab keys or buttons or actively grab
the keyboard or pointer should use the
-following (xI routines rather than the corresponding Xlib
+following Intrinsics routines rather than the corresponding Xlib
routines.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To passively grab a single key of the keyboard, use
-<function>XtGrabKey .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtGrabKey" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtGrabKey(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>keycode</emphasis>, <emphasis remap='I'>modifiers</emphasis>, \
-<emphasis remap='I'>owner_events</emphasis>, <emphasis remap='I'>pointer_mode</emphasis>, <emphasis remap='I'>keyboard_mode</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- KeyCode <emphasis remap='I'>keycode</emphasis>;
-<!-- .br -->
- Modifiers <emphasis remap='I'>modifiers</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>owner_events</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>pointer_mode</emphasis>, <emphasis remap='I'>keyboard_mode</emphasis>;
-<!-- .FN -->
+<function>XtGrabKey</function>.
+</para>
+
+<funcsynopsis id='XtGrabKey'>
+<funcprototype>
+<funcdef>void <function>XtGrabKey</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>KeyCode <parameter>keycode</parameter></paramdef>
+ <paramdef>Modifiers <parameter>modifiers</parameter></paramdef>
+ <paramdef>Boolean <parameter>owner_events</parameter></paramdef>
+ <paramdef>int <parameter>pointer_mode</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1227,8 +1038,7 @@ void XtGrabKey(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>keycod
</term>
<listitem>
<para>
-Specifies the widget in whose window the key is to be grabbed. (cI
-<!-- .sp 6p -->
+Specifies the widget in whose window the key is to be grabbed. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -1237,10 +1047,7 @@ Specifies the widget in whose window the key is to be grabbed. (cI
<emphasis remap='I'>keycode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1248,10 +1055,8 @@ Specifies the widget in whose window the key is to be grabbed. (cI
<emphasis remap='I'>modifiers</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1259,10 +1064,8 @@ Specifies the widget in whose window the key is to be grabbed. (cI
<emphasis remap='I'>owner_events</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1270,10 +1073,8 @@ Specifies the widget in whose window the key is to be grabbed. (cI
<emphasis remap='I'>pointer_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1283,22 +1084,20 @@ Specifies the widget in whose window the key is to be grabbed. (cI
<listitem>
<para>
Specify arguments to
-<function>XGrabKey ;</function>
-see Section 12.2 in <emphasis remap='I'>(xL</emphasis>.
+<function>XGrabKey</function>;
+see Section 12.2 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtGrabKey</function>
calls
<function>XGrabKey</function>
specifying the widget's window as the grab
window if the widget is realized. The remaining arguments are exactly
as for
-<function>XGrabKey .</function>
+<function>XGrabKey</function>.
If the widget is not realized, or is later unrealized, the call to
<function>XGrabKey</function>
is performed (again) when
@@ -1310,9 +1109,9 @@ is called with a
event matching the specified keycode and modifiers (which may be
<function>AnyKey</function>
or
-<function>AnyModifier ,</function>
+<function>AnyModifier</function>,
respectively) for the
-widget's window, the (xI will call
+widget's window, the Intrinsics will call
<function>XtUngrabKeyboard</function>
with the timestamp from the
<function>KeyPress</function>
@@ -1330,31 +1129,24 @@ grabbed, or
<para>
<function>XFilterEvent</function>
returns
-<function>True .</function>
-
-<!-- .sp -->
+<function>True</function>.
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
To cancel a passive key grab, use
-<function>XtUngrabKey .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtUngrabKey" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtUngrabKey(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>keycode</emphasis><emphasis remap='I'>, modifiers</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- KeyCode <emphasis remap='I'>keycode</emphasis>;
-<!-- .br -->
- Modifiers <emphasis remap='I'>modifiers</emphasis>;
-<!-- .FN -->
+<function>XtUngrabKey</function>.
+</para>
+
+<funcsynopsis id='XtUngrabKey'>
+<funcprototype>
+<funcdef>void <function>XtUngrabKey</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>KeyCode <parameter>keycode</parameter></paramdef>
+ <paramdef>Modifiers <parameter>modifiers</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1363,7 +1155,6 @@ void XtUngrabKey(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>keyc
<listitem>
<para>
Specifies the widget in whose window the key was grabbed.
-<!-- .sp 6p -->
</para>
</listitem>
</varlistentry>
@@ -1372,10 +1163,8 @@ Specifies the widget in whose window the key was grabbed.
<emphasis remap='I'>keycode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1385,15 +1174,13 @@ Specifies the widget in whose window the key was grabbed.
<listitem>
<para>
Specify arguments to
-<function>XUngrabKey ;</function>
-see Section 12.2 in <emphasis remap='I'>(xL</emphasis>.
+<function>XUngrabKey</function>;
+see Section 12.2 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtUngrabKey</function>
procedure calls
@@ -1401,37 +1188,29 @@ procedure calls
specifying the widget's
window as the ungrab window if the widget is realized. The remaining
arguments are exactly as for
-<function>XUngrabKey .</function>
+<function>XUngrabKey</function>.
If the widget is not realized,
<function>XtUngrabKey</function>
removes a deferred
<function>XtGrabKey</function>
request, if any, for the specified widget, keycode, and modifiers.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To actively grab the keyboard, use
-<function>XtGrabKeyboard .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtGrabKeyboard" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-int XtGrabKeyboard(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>owner_events</emphasis>, <emphasis remap='I'>pointer_mode</emphasis>, \
-<emphasis remap='I'>keyboard_mode</emphasis>, <emphasis remap='I'>time</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>owner_events</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>pointer_mode</emphasis>, <emphasis remap='I'>keyboard_mode</emphasis>;
-<!-- .br -->
- Time <emphasis remap='I'>time</emphasis>;
-<!-- .br -->
-<!-- .FN -->
+<function>XtGrabKeyboard</function>.
+</para>
+
+<funcsynopsis id='XtGrabKeyboard'>
+<funcprototype>
+<funcdef>int <function>XtGrabKeyboard</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>Boolean <parameter>owner_events</parameter></paramdef>
+ <paramdef>int <parameter>pointer_mode</parameter></paramdef>
+ <paramdef>Time <parameter>time</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1440,8 +1219,7 @@ int XtGrabKeyboard(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>ow
<listitem>
<para>
Specifies the widget for whose window the keyboard is to be grabbed.
-(cI
-<!-- .sp 6p -->
+Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -1450,10 +1228,8 @@ Specifies the widget for whose window the keyboard is to be grabbed.
<emphasis remap='I'>owner_events</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1461,10 +1237,8 @@ Specifies the widget for whose window the keyboard is to be grabbed.
<emphasis remap='I'>pointer_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1472,10 +1246,8 @@ Specifies the widget for whose window the keyboard is to be grabbed.
<emphasis remap='I'>keyboard_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1485,47 +1257,41 @@ Specifies the widget for whose window the keyboard is to be grabbed.
<listitem>
<para>
Specify arguments to
-<function>XGrabKeyboard ;</function>
-see Section 12.2 in <emphasis remap='I'>(xL</emphasis>.
+<function>XGrabKeyboard</function>;
+see Section 12.2 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
If the specified widget is realized,
<function>XtGrabKeyboard</function>
calls
<function>XGrabKeyboard</function>
specifying the widget's window as the grab window. The remaining
arguments and return value are exactly as for
-<function>XGrabKeyboard .</function>
+<function>XGrabKeyboard</function>.
If the widget is not realized,
<function>XtGrabKeyboard</function>
immediately returns
-<function>GrabNotViewable .</function>
+<function>GrabNotViewable</function>.
No future automatic ungrab is implied by
-<function>XtGrabKeyboard .</function>
-<!-- .sp -->
+<function>XtGrabKeyboard</function>.
</para>
+
<para>
-<!-- .LP -->
To cancel an active keyboard grab, use
-<function>XtUngrabKeyboard .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtUngrabKeyboard" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtUngrabKeyboard</function>.
</para>
-<!-- .FD 0 -->
-void XtUngrabKeyboard(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>time</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- Time <emphasis remap='I'>time</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtUngrabKeyboard'>
+<funcprototype>
+<funcdef>void <function>XtUngrabKeyboard</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>Time <parameter>time</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1544,52 +1310,38 @@ Specifies the widget that has the active keyboard grab.
<listitem>
<para>
Specifies the additional argument to
-<function>XUngrabKeyboard ;</function>
-see Section 12.2 in <emphasis remap='I'>(xL</emphasis>.
+<function>XUngrabKeyboard</function>;
+see Section 12.2 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtUngrabKeyboard</function>
calls
<function>XUngrabKeyboard</function>
with the specified time.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To passively grab a single pointer button, use
-<function>XtGrabButton .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtGrabButton" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtGrabButton(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>button</emphasis>, <emphasis remap='I'>modifiers</emphasis>, \
-<emphasis remap='I'>owner_events</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>pointer_mode</emphasis>,
- <emphasis remap='I'>keyboard_mode</emphasis>, <emphasis remap='I'>confine_to</emphasis>, <emphasis remap='I'>cursor</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>button</emphasis>;
-<!-- .br -->
- Modifiers <emphasis remap='I'>modifiers</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>owner_events</emphasis>;
-<!-- .br -->
- unsigned int <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>pointer_mode</emphasis>, <emphasis remap='I'>keyboard_mode</emphasis>;
-<!-- .br -->
- Window <emphasis remap='I'>confine_to</emphasis>;
-<!-- .br -->
- Cursor <emphasis remap='I'>cursor</emphasis>;
-<!-- .FN -->
+<function>XtGrabButton</function>.
+</para>
+
+<funcsynopsis id='XtGrabButton'>
+<funcprototype>
+<funcdef>void <function>XtGrabButton</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>int <parameter>button</parameter></paramdef>
+ <paramdef>Modifiers <parameter>modifiers</parameter></paramdef>
+ <paramdef>Boolean <parameter>owner_events</parameter></paramdef>
+ <paramdef>unsigned int <parameter>event_mask</parameter></paramdef>
+ <paramdef>int <parameter>pointer_mode</parameter></paramdef>
+ <paramdef>Window <parameter>confine_to</parameter></paramdef>
+ <paramdef>Cursor <parameter>cursor</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1597,8 +1349,7 @@ void XtGrabButton(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>but
</term>
<listitem>
<para>
-Specifies the widget in whose window the button is to be grabbed. (cI
-<!-- .sp 6p -->
+Specifies the widget in whose window the button is to be grabbed. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -1607,10 +1358,7 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>button</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1618,10 +1366,8 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>modifiers</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1629,10 +1375,8 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>owner_events</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1640,10 +1384,8 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>event_mask</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1651,10 +1393,8 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>pointer_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1662,10 +1402,8 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>keyboard_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1673,10 +1411,8 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<emphasis remap='I'>confine_to</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
+
</listitem>
</varlistentry>
<varlistentry>
@@ -1686,22 +1422,20 @@ Specifies the widget in whose window the button is to be grabbed. (cI
<listitem>
<para>
Specify arguments to
-<function>XGrabButton ;</function>
-see Section 12.1 in <emphasis remap='I'>(xL</emphasis>.
+<function>XGrabButton</function>;
+see Section 12.1 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtGrabButton</function>
calls
<function>XGrabButton</function>
specifying the widget's window as the
grab window if the widget is realized. The remaining arguments are
exactly as for
-<function>XGrabButton .</function>
+<function>XGrabButton</function>.
If the widget is not realized, or is later unrealized, the call to
<function>XGrabButton</function>
is performed (again)
@@ -1713,9 +1447,9 @@ is called with a
event matching the specified button and modifiers (which may be
<function>AnyButton</function>
or
-<function>AnyModifier ,</function>
+<function>AnyModifier</function>,
respectively)
-for the widget's window, the (xI will call
+for the widget's window, the Intrinsics will call
<function>XtUngrabPointer</function>
with the timestamp from the
<function>ButtonPress</function>
@@ -1733,31 +1467,24 @@ not previously grabbed, or
<para>
<function>XFilterEvent</function>
returns
-<function>True .</function>
-
-<!-- .sp -->
+<function>True</function>.
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
To cancel a passive button grab, use
-<function>XtUngrabButton .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtUngrabButton" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtUngrabButton(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>button</emphasis>, <emphasis remap='I'>modifiers</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- unsigned int <emphasis remap='I'>button</emphasis>;
-<!-- .br -->
- Modifiers <emphasis remap='I'>modifiers</emphasis>;
-<!-- .FN -->
+<function>XtUngrabButton</function>.
+</para>
+
+<funcsynopsis id='XtUngrabButton'>
+<funcprototype>
+<funcdef>void <function>XtUngrabButton</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>unsigned int <parameter>button</parameter></paramdef>
+ <paramdef>Modifiers <parameter>modifiers</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1774,10 +1501,7 @@ Specifies the widget in whose window the button was grabbed.
<emphasis remap='I'>button</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1787,15 +1511,13 @@ Specifies the widget in whose window the button was grabbed.
<listitem>
<para>
Specify arguments to
-<function>XUngrabButton ;</function>
-see Section 12.1 in <emphasis remap='I'>(xL</emphasis>.
+<function>XUngrabButton</function>;
+see Section 12.1 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtUngrabButton</function>
procedure calls
@@ -1803,43 +1525,32 @@ procedure calls
specifying the
widget's window as the ungrab window if the widget is realized. The
remaining arguments are exactly as for
-<function>XUngrabButton .</function>
+<function>XUngrabButton</function>.
If the widget is not realized,
<function>XtUngrabButton</function>
removes a deferred
<function>XtGrabButton</function>
request, if any, for the specified widget, button, and modifiers.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To actively grab the pointer, use
-<function>XtGrabPointer .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtGrabPointer" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-int XtGrabPointer(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>owner_events</emphasis>, <emphasis remap='I'>event_mask</emphasis>, \
-<emphasis remap='I'>pointer_mode</emphasis>, <emphasis remap='I'>keyboard_mode</emphasis>,
- <emphasis remap='I'>confine_to</emphasis>, <emphasis remap='I'>cursor</emphasis>, <emphasis remap='I'>time</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>owner_events</emphasis>;
-<!-- .br -->
- unsigned int <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>pointer_mode</emphasis>, <emphasis remap='I'>keyboard_mode</emphasis>;
-<!-- .br -->
- Window <emphasis remap='I'>confine_to</emphasis>;
-<!-- .br -->
- Cursor <emphasis remap='I'>cursor</emphasis>;
-<!-- .br -->
- Time <emphasis remap='I'>time</emphasis>;
-<!-- .FN -->
+<function>XtGrabPointer</function>.
+</para>
+
+<funcsynopsis id='XtGrabPointer'>
+<funcprototype>
+<funcdef>int <function>XtGrabPointer</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>Boolean <parameter>owner_events</parameter></paramdef>
+ <paramdef>unsigned int <parameter>event_mask</parameter></paramdef>
+ <paramdef>int <parameter>pointer_mode</parameter></paramdef>
+ <paramdef>Window <parameter>confine_to</parameter></paramdef>
+ <paramdef>Cursor <parameter>cursor</parameter></paramdef>
+ <paramdef>Time <parameter>time</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1847,8 +1558,7 @@ int XtGrabPointer(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>own
</term>
<listitem>
<para>
-Specifies the widget for whose window the pointer is to be grabbed. (cI
-<!-- .sp 6p -->
+Specifies the widget for whose window the pointer is to be grabbed. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -1857,10 +1567,7 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<emphasis remap='I'>owner_events</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1868,10 +1575,7 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<emphasis remap='I'>event_mask</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1879,10 +1583,7 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<emphasis remap='I'>pointer_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1890,10 +1591,7 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<emphasis remap='I'>keyboard_mode</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1901,10 +1599,7 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<emphasis remap='I'>confine_to</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1912,10 +1607,7 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<emphasis remap='I'>cursor</emphasis>
</term>
<listitem>
- <para>
-<!-- .br -->
-<!-- .ns -->
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1925,47 +1617,41 @@ Specifies the widget for whose window the pointer is to be grabbed. (cI
<listitem>
<para>
Specify arguments to
-<function>XGrabPointer ;</function>
-see Section 12.1 in <emphasis remap='I'>(xL</emphasis>.
+<function>XGrabPointer</function>;
+see Section 12.1 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
If the specified widget is realized,
<function>XtGrabPointer</function>
calls
-<function>XGrabPointer ,</function>
+<function>XGrabPointer</function>,
specifying the widget's window as the grab window. The remaining
arguments and return value are exactly as for
-<function>XGrabPointer .</function>
+<function>XGrabPointer</function>.
If the widget is not realized,
<function>XtGrabPointer</function>
immediately returns
-<function>GrabNotViewable .</function>
+<function>GrabNotViewable</function>.
No future automatic ungrab is implied by
-<function>XtGrabPointer .</function>
-<!-- .sp -->
+<function>XtGrabPointer</function>.
</para>
+
<para>
-<!-- .LP -->
To cancel an active pointer grab, use
-<function>XtUngrabPointer .</function>
+<function>XtUngrabPointer</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtUngrabPointer" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtUngrabPointer(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>time</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- Time <emphasis remap='I'>time</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtUngrabPointer'>
+<funcprototype>
+<funcdef>void <function>XtUngrabPointer</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>Time <parameter>time</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -1984,46 +1670,38 @@ Specifies the widget that has the active pointer grab.
<listitem>
<para>
Specifies the time argument to
-<function>XUngrabPointer ;</function>
-see Section 12.1 in <emphasis remap='I'>(xL</emphasis>.
+<function>XUngrabPointer</function>;
+see Section 12.1 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtUngrabPointer</function>
calls
<function>XUngrabPointer</function>
with the specified time.
-
</para>
-</sect3>
</sect2>
-<sect2 id="Focusing_Events_on_a_Child">
+</sect1>
+
+<sect1 id="Focusing_Events_on_a_Child">
<title>Focusing Events on a Child</title>
-<!-- .XS -->
-<!-- <function>(SN Focusing Events on a Child</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To redirect keyboard input to a normal descendant of a
widget without calling
-<function>XSetInputFocus ,</function>
+<function>XSetInputFocus</function>,
use
-<function>XtSetKeyboardFocus .</function>
+<function>XtSetKeyboardFocus</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtSetKeyboardFocus" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtSetKeyboardFocus(<emphasis remap='I'>subtree</emphasis>\, <emphasis remap='I'>descendant</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>subtree</emphasis>, <emphasis remap='I'>descendant</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtSetKeyboardFocus'>
+<funcprototype>
+<funcdef>void <function>XtSetKeyboardFocus</function></funcdef>
+ <paramdef>Widget <parameter>subtree</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2032,7 +1710,7 @@ void XtSetKeyboardFocus(<emphasis remap='I'>subtree</emphasis>\, <emphasis remap
<listitem>
<para>
Specifies the subtree of the hierarchy for which the keyboard focus is
-to be set. (cI
+to be set. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -2044,17 +1722,15 @@ to be set. (cI
<para>
Specifies either the normal (non-pop-up) descendant of <emphasis remap='I'>subtree</emphasis> to which
keyboard events are logically directed, or
-<function>None .</function>
+<function>None</function>.
It is not an error to specify
<function>None</function>
-when no input focus was previously set. (oI
+when no input focus was previously set. Must be of class Object or any subclass thereof.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtSetKeyboardFocus</function>
causes
<function>XtDispatchEvent</function>
@@ -2063,8 +1739,8 @@ and dispatch them to the specified descendant widget or to an ancestor.
If the descendant's class is not a subclass of Core, the descendant is
replaced by its closest windowed ancestor.
</para>
+
<para>
-<!-- .LP -->
When there is no modal cascade, keyboard events can be dispatched
to a widget in one of five ways. Assume the server delivered the
event to the window for widget E (because of X input focus, key or
@@ -2094,7 +1770,6 @@ redirected the keyboard focus or E if no such ancestor exists, if
the target of that focus redirection has in turn redirected the
keyboard focus, recursively follow this focus chain to find a widget
F that has not redirected focus.
-<!-- .RS -->
</para>
</listitem>
<listitem>
@@ -2116,7 +1791,6 @@ is called.
<listitem>
<para>
If E is an ancestor of F, and the event is a key press, and either
-<!-- .RS -->
</para>
</listitem>
<listitem>
@@ -2124,7 +1798,7 @@ If E is an ancestor of F, and the event is a key press, and either
E has grabbed the key with
<function>XtGrabKey</function>
and <emphasis remap='I'>owner_events</emphasis>
-<function>False ,</function>
+<function>False</function>,
or
</para>
</listitem>
@@ -2133,17 +1807,15 @@ or
E has grabbed the key with
<function>XtGrabKey</function>
and <emphasis remap='I'>owner_events</emphasis>
-<function>True ,</function>
+<function>True</function>,
and the coordinates of the event are outside the rectangle specified
by E's geometry,
-<!-- .RE -->
then the event is dispatched to E.
</para>
</listitem>
<listitem>
<para>
Otherwise, define A as the closest common ancestor of E and F:
-<!-- .RS -->
</para>
</listitem>
<listitem>
@@ -2163,23 +1835,20 @@ and any value of <emphasis remap='I'>owner_events</emphasis>, the event is dispa
<para>
Else, the event is dispatched to the ancestor of F closest to A
that has grabbed the key and modifier combination with
-<function>XtGrabKey .</function>
-<!-- .RE -->
-<!-- .RE -->
+<function>XtGrabKey</function>.
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
When there is a modal cascade, if the final destination widget as
identified above is in the active subset of the cascade, the event is
dispatched; otherwise the event is remapped to a spring-loaded shell
or discarded.
-Regardless of where it is dispatched, the (xI do not modify
+Regardless of where it is dispatched, the Intrinsics do not modify
the contents of the event.
</para>
+
<para>
-<!-- .LP -->
When <emphasis remap='I'>subtree</emphasis> or one of its descendants acquires the X input focus
or the pointer moves into the subtree such that keyboard events would
now be delivered to the subtree, a
@@ -2193,31 +1862,27 @@ or the keyboard focus for one of its ancestors, a
event is generated for descendant if
<function>FocusChange</function>
events have been selected by the descendant.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
A widget tree may also actively manage the X server input focus. To
do so, a widget class specifies an accept_focus procedure.
</para>
+
<para>
-<!-- .LP -->
-<!-- .IN "accept_focus procedure" -->
The accept_focus procedure pointer is of type
-<function>XtAcceptFocusProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAcceptFocusProc" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtAcceptFocusProc</function>.
</para>
-<!-- .FD 0 -->
-typedef Boolean (*XtAcceptFocusProc)(Widget, Time*);
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- Time *<emphasis remap='I'>time</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAcceptFocusProc'>
+<funcprototype>
+<funcdef>Boolean <function>*XtAcceptFocusProc</function></funcdef>
+
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>Time *<parameter>time</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2241,11 +1906,9 @@ Specifies the X time of the event causing the accept focus.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
Widgets that need the input focus can call
<function>XSetInputFocus</function>
-explicitly, pursuant to the restrictions of the <emphasis remap='I'>(xC</emphasis>.
+explicitly, pursuant to the restrictions of the <emphasis remap='I'>Inter-Client Communication Conventions Manual.</emphasis>.
To allow outside agents, such as the parent,
to cause a widget to take the input focus,
every widget exports an accept_focus procedure.
@@ -2261,25 +1924,21 @@ and
events).
Widgets classes that never want the input focus should set the
<emphasis remap='I'>accept_focus</emphasis> field to NULL.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To call a widget's accept_focus procedure, use
-<function>XtCallAcceptFocus .</function>
+<function>XtCallAcceptFocus</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtCallAcceptFocus" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-Boolean XtCallAcceptFocus(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>time</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- Time *<emphasis remap='I'>time</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtCallAcceptFocus'>
+<funcprototype>
+<funcdef>Boolean <function>XtCallAcceptFocus</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>Time *<parameter>time</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2287,7 +1946,7 @@ Boolean XtCallAcceptFocus(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>
</term>
<listitem>
<para>
-Specifies the widget. (cI
+Specifies the widget. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -2303,8 +1962,6 @@ Specifies the X time of the event that is causing the focus change.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtCallAcceptFocus</function>
function calls the specified widget's accept_focus procedure,
@@ -2313,16 +1970,11 @@ procedure returns.
If <emphasis remap='I'>accept_focus</emphasis> is NULL,
<function>XtCallAcceptFocus</function>
returns
-<function>False .</function>
-
+<function>False</function>.
</para>
-<sect3 id="Events_for_Drawables_That_Are_Not_a_Widget_s_Window">
+<sect2 id="Events_for_Drawables_That_Are_Not_a_Widget_s_Window">
<title>Events for Drawables That Are Not a Widget's Window</title>
-<!-- .XS -->
-<!-- <function>(SN Events for Drawables That Are Not a Widget's Window</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Sometimes an application must handle events for drawables that are not
associated with widgets in its widget tree. Examples include handling
<function>GraphicsExpose</function>
@@ -2332,25 +1984,21 @@ events on Pixmaps, and handling
<function>PropertyNotify</function>
events on the root window.
</para>
+
<para>
-<!-- .LP -->
-To register a drawable with the (xI event dispatching, use
-<function>XtRegisterDrawable .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRegisterDrawable" "" "@DEF@" -->
-<!-- .sM -->
+To register a drawable with the Intrinsics event dispatching, use
+<function>XtRegisterDrawable</function>.
</para>
-<!-- .FD 0 -->
-void XtRegisterDrawable(<emphasis remap='I'>display</emphasis>, <emphasis remap='I'>drawable</emphasis>, <emphasis remap='I'>widget</emphasis>)
-<!-- .br -->
- Display *<emphasis remap='I'>display</emphasis>;
-<!-- .br -->
- Drawable <emphasis remap='I'>drawable</emphasis>;
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRegisterDrawable'>
+<funcprototype>
+<funcdef>void <function>XtRegisterDrawable</function></funcdef>
+ <paramdef>Display *<parameter>display</parameter></paramdef>
+ <paramdef>Drawable <parameter>drawable</parameter></paramdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2384,8 +2032,6 @@ Specifies the widget to register the drawable for.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtRegisterDrawable</function>
associates the specified drawable with the specified widget
so that future calls to
@@ -2395,32 +2041,28 @@ The default event dispatcher will dispatch future events that
arrive for the drawable to the widget in the same manner as
events that contain the widget's window.
</para>
+
<para>
-<!-- .LP -->
If the drawable is already registered with another widget, or if the
drawable is the window of a widget in the client's widget tree, the
results of calling
<function>XtRegisterDrawable</function>
are undefined.
-
</para>
+
<para>
-<!-- .LP -->
To unregister a drawable with the Intrinsics event dispatching, use
-<function>XtUnregisterDrawable .</function>
+<function>XtUnregisterDrawable</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtUnregisterDrawable" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtUnregisterDrawable(<emphasis remap='I'>display</emphasis>, <emphasis remap='I'>drawable</emphasis>)
-<!-- .br -->
- Display *<emphasis remap='I'>display</emphasis>;
-<!-- .br -->
- Drawable <emphasis remap='I'>drawable</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtUnregisterDrawable'>
+<funcprototype>
+<funcdef>void <function>XtUnregisterDrawable</function></funcdef>
+ <paramdef>Display *<parameter>display</parameter></paramdef>
+ <paramdef>Drawable <parameter>drawable</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2444,53 +2086,43 @@ Specifies the drawable to unregister.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtUnregisterDrawable</function>
removes an association created with
-<function>XtRegisterDrawable .</function>
+<function>XtRegisterDrawable</function>.
If the drawable is the window of a widget in the client's widget tree
the results of calling
<function>XtUnregisterDrawable</function>
are undefined.
-
</para>
-</sect3>
</sect2>
-<sect2 id="Querying_Event_Sources">
+</sect1>
+
+<sect1 id="Querying_Event_Sources">
<title>Querying Event Sources</title>
-<!-- .XS -->
-<!-- <function>(SN Querying Event Sources</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
The event manager provides several functions to examine and read events
(including file and timer events) that are in the queue.
-The next three functions are (xI equivalents of the
-<function>XPending ,</function>
-<function>XPeekEvent ,</function>
+The next three functions are Intrinsics equivalents of the
+<function>XPending</function>,
+<function>XPeekEvent</function>,
and
<function>XNextEvent</function>
Xlib calls.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
-<!-- .IN "Events" -->
To determine if there are any events on the input queue for a given application,
use
-<function>XtAppPending .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppPending" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtAppPending</function>.
</para>
-<!-- .FD 0 -->
-XtInputMask XtAppPending(<emphasis remap='I'>app_context</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppPending'>
+<funcprototype>
+<funcdef>XtInputMask <function>XtAppPending</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2504,17 +2136,15 @@ Specifies the application context that identifies the application to check.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppPending</function>
function returns a nonzero value if there are
events pending from the X server, timer pending, other input sources
pending, or signal sources pending. The
value returned is a bit mask that is the OR of
-<function>XtIMXEvent ,</function>
-<function>XtIMTimer ,</function>
-<function>XtIMAlternateInput ,</function>
+<function>XtIMXEvent</function>,
+<function>XtIMTimer</function>,
+<function>XtIMAlternateInput</function>,
and
<function>XtIMSignal</function>
(see
@@ -2523,26 +2153,22 @@ If there are no events pending,
<function>XtAppPending</function>
flushes the output buffers of each Display in the application context
and returns zero.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To return the event from the head of a given application's input queue
without removing input from the queue, use
-<function>XtAppPeekEvent .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppPeekEvent" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtAppPeekEvent</function>.
</para>
-<!-- .FD 0 -->
-Boolean XtAppPeekEvent(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>event_return</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- XEvent *<emphasis remap='I'>event_return</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppPeekEvent'>
+<funcprototype>
+<funcdef>Boolean <function>XtAppPeekEvent</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>XEvent *<parameter>event_return</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2566,12 +2192,10 @@ Returns the event information to the specified event structure.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
If there is an X event in the queue,
<function>XtAppPeekEvent</function>
copies it into <emphasis remap='I'>event_return</emphasis> and returns
-<function>True .</function>
+<function>True</function>.
If no X input is on the queue,
<function>XtAppPeekEvent</function>
flushes the output buffers of each Display in the application context
@@ -2580,15 +2204,14 @@ and blocks until some input is available
If the next available input is an X event,
<function>XtAppPeekEvent</function>
fills in <emphasis remap='I'>event_return</emphasis> and returns
-<function>True .</function>
+<function>True</function>.
Otherwise, the input is for an input source
registered with
-<function>XtAppAddInput ,</function>
+<function>XtAppAddInput</function>,
and
<function>XtAppPeekEvent</function>
returns
-<function>False .</function>
-<!-- .FS -->
+<function>False</function>.
The sample implementations provides XtAppPeekEvent as described. Timeout callbacks
are called while blocking for input. If some input for an input source is
available,
@@ -2596,28 +2219,23 @@ available,
will return
<function>True</function>
without returning an event.
-<!-- .FE -->
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To remove and return the event
from the head of a given application's X event queue,
use
-<function>XtAppNextEvent .</function>
+<function>XtAppNextEvent</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppNextEvent" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAppNextEvent(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>event_return</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- XEvent *<emphasis remap='I'>event_return</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppNextEvent'>
+<funcprototype>
+<funcdef>void <function>XtAppNextEvent</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>XEvent *<parameter>event_return</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2641,8 +2259,6 @@ Returns the event information to the specified event structure.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
If the X event queue is empty,
<function>XtAppNextEvent</function>
flushes the X output buffers of each Display in the application context
@@ -2650,17 +2266,13 @@ and waits for an X event while looking at the other input sources
and timeout values and calling any callback procedures triggered by them.
This wait time can be used for background processing;
see Section 7.8.
-
</para>
-</sect2>
-<sect2 id="Dispatching_Events">
+</sect1>
+
+<sect1 id="Dispatching_Events">
<title>Dispatching Events</title>
-<!-- .XS -->
-<!-- <function>(SN Dispatching Events</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-The (xI provide functions that dispatch events
+The Intrinsics provide functions that dispatch events
to widgets or other application code.
Every client interested in X events on a widget uses
<function>XtAddEventHandler</function>
@@ -2669,26 +2281,22 @@ interested in and a procedure (event handler) to be called
when the event happens in that window.
The translation manager automatically registers event handlers for widgets
that use translation tables; see Chapter 10.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
Applications that need direct control of the processing of different types
of input should use
-<function>XtAppProcessEvent .</function>
+<function>XtAppProcessEvent</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppProcessEvent" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAppProcessEvent(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>mask</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- XtInputMask <emphasis remap='I'>mask</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppProcessEvent'>
+<funcprototype>
+<funcdef>void <function>XtAppProcessEvent</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>XtInputMask <parameter>mask</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2709,11 +2317,11 @@ application for which to process input.
<para>
Specifies what types of events to process.
The mask is the bitwise inclusive OR of any combination of
-<function>XtIMXEvent ,</function>
-<function>XtIMTimer ,</function>
-<function>XtIMAlternateInput ,</function>
+<function>XtIMXEvent</function>,
+<function>XtIMTimer</function>,
+<function>XtIMAlternateInput</function>,
and
-<function>XtIMSignal .</function>
+<function>XtIMSignal</function>.
As a convenience,
<function>Intrinsic.h</function>
defines the symbolic name
@@ -2724,8 +2332,6 @@ to be the bitwise inclusive OR of these four event types.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppProcessEvent</function>
function processes one timer, input source, signal source, or X event.
@@ -2735,46 +2341,42 @@ blocks until there is.
If there is more than one type of input available to process,
it is undefined which will get processed.
Usually, this procedure is not called by client applications; see
-<function>XtAppMainLoop .</function>
+<function>XtAppMainLoop</function>.
<function>XtAppProcessEvent</function>
processes timer events by calling any appropriate timer callbacks,
input sources by calling any appropriate input callbacks,
signal source by calling any appropriate signal callbacks,
and X events by
calling
-<function>XtDispatchEvent .</function>
+<function>XtDispatchEvent</function>.
</para>
+
<para>
-<!-- .LP -->
When an X event is received,
it is passed to
-<function>XtDispatchEvent ,</function>
+<function>XtDispatchEvent</function>,
which calls the appropriate event handlers
and passes them the widget, the event, and client-specific data
registered with each procedure.
If no handlers for that event are registered,
the event is ignored and the dispatcher simply returns.
-
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To dispatch an event returned by
-<function>XtAppNextEvent ,</function>
+<function>XtAppNextEvent</function>,
retrieved directly from the Xlib queue, or synthetically constructed,
to any registered event filters or event handlers, call
-<function>XtDispatchEvent .</function>
+<function>XtDispatchEvent</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtDispatchEvent" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-Boolean XtDispatchEvent(<emphasis remap='I'>event</emphasis>)
-<!-- .br -->
- XEvent *<emphasis remap='I'>event</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtDispatchEvent'>
+<funcprototype>
+<funcdef>Boolean <function>XtDispatchEvent</function></funcdef>
+ <paramdef>XEvent *<parameter>event</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2789,15 +2391,13 @@ to the appropriate event handlers.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtDispatchEvent</function>
function first calls
<function>XFilterEvent</function>
with the <emphasis remap='I'>event</emphasis> and the window of the widget to which the
-(xI intend to dispatch the event, or the event window if
-the (xI would not dispatch the event to any handlers.
+Intrinsics intend to dispatch the event, or the event window if
+the Intrinsics would not dispatch the event to any handlers.
If
<function>XFilterEvent</function>
returns
@@ -2806,14 +2406,14 @@ and the event activated a server grab as identified
by a previous call to
<function>XtGrabKey</function>
or
-<function>XtGrabButton ,</function>
+<function>XtGrabButton</function>,
<function>XtDispatchEvent</function>
calls
<function>XtUngrabKeyboard</function>
or
<function>XtUngrabPointer</function>
with the timestamp from the event and immediately returns
-<function>True .</function>
+<function>True</function>.
If
<function>XFilterEvent</function>
returns
@@ -2821,7 +2421,7 @@ returns
and a grab was not activated,
<function>XtDispatchEvent</function>
just immediately returns
-<function>True .</function>
+<function>True</function>.
Otherwise,
<function>XtDispatchEvent</function>
sends the event to the event handler functions that
@@ -2832,7 +2432,7 @@ returns
if
<function>XFilterEvent</function>
returned
-<function>True ,</function>
+<function>True</function>,
or if the event was dispatched to some handler, and
<function>False</function>
if it found no handler to which to dispatch the event.
@@ -2842,9 +2442,9 @@ contains a timestamp (see
<function>XtLastTimestampProcessed ),</function>
regardless of whether it was filtered or dispatched.
If a modal cascade is active with <emphasis remap='I'>spring_loaded</emphasis>
-<function>True ,</function>
+<function>True</function>,
and if the event is a remap event as defined by
-<function>XtAddGrab ,</function>
+<function>XtAddGrab</function>,
<function>XtDispatchEvent</function>
may dispatch the event a second time. If it does so,
<function>XtDispatchEvent</function>
@@ -2854,32 +2454,26 @@ again with the window of the spring-loaded widget prior to the second
dispatch, and if
<function>XFilterEvent</function>
returns
-<function>True ,</function>
+<function>True</function>,
the second dispatch will not be performed.
-
</para>
-</sect2>
-<sect2 id="The_Application_Input_Loop">
+</sect1>
+
+<sect1 id="The_Application_Input_Loop">
<title>The Application Input Loop</title>
-<!-- .XS -->
-<!-- <function>(SN The Application Input Loop</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To process all input from a given application in a continuous loop,
use the convenience procedure
-<function>XtAppMainLoop .</function>
+<function>XtAppMainLoop</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppMainLoop" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAppMainLoop(<emphasis remap='I'>app_context</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppMainLoop'>
+<funcprototype>
+<funcdef>void <function>XtAppMainLoop</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -2893,18 +2487,16 @@ Specifies the application context that identifies the application.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppMainLoop</function>
function first reads the next incoming X event by calling
<function>XtAppNextEvent</function>
and then dispatches the event to the appropriate registered procedure
by calling
-<function>XtDispatchEvent .</function>
+<function>XtDispatchEvent</function>.
This constitutes the main loop of (tk applications.
There is nothing special about
-<function>XtAppMainLoop ;</function>
+<function>XtAppMainLoop</function>;
it simply calls
<function>XtAppNextEvent</function>
and then
@@ -2916,55 +2508,50 @@ If the flag is set, the loop breaks.
The whole loop is enclosed between a matching
<function>XtAppLock</function>
and
-<function>XtAppUnlock .</function>
+<function>XtAppUnlock</function>.
</para>
+
<para>
-<!-- .LP -->
Applications can provide their own version of this loop,
which tests some global termination flag or tests that the number
of top-level widgets is larger than zero before circling back to the call to
-<function>XtAppNextEvent .</function>
-
+<function>XtAppNextEvent</function>.
</para>
-</sect2>
-<sect2 id="Setting_and_Checking_the_Sensitivity_State_of_a_Widget">
+</sect1>
+
+<sect1 id="Setting_and_Checking_the_Sensitivity_State_of_a_Widget">
<title>Setting and Checking the Sensitivity State of a Widget</title>
-<!-- .XS -->
-<!-- <function>(SN Setting and Checking the Sensitivity State of a Widget</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Many widgets have a mode in which they assume a different appearance
(for example, are grayed out or stippled), do not respond to user events,
and become dormant.
</para>
+
<para>
-<!-- .LP -->
When dormant,
a widget is considered to be insensitive.
If a widget is insensitive,
the event manager does not dispatch any events to the widget
with an event type of
-<function>KeyPress ,</function>
-<function>KeyRelease ,</function>
-<function>ButtonPress ,</function>
-<function>ButtonRelease ,</function>
-<function>MotionNotify ,</function>
-<function>EnterNotify ,</function>
-<function>LeaveNotify ,</function>
-<function>FocusIn ,</function>
+<function>KeyPress</function>,
+<function>KeyRelease</function>,
+<function>ButtonPress</function>,
+<function>ButtonRelease</function>,
+<function>MotionNotify</function>,
+<function>EnterNotify</function>,
+<function>LeaveNotify</function>,
+<function>FocusIn</function>,
or
-<function>FocusOut .</function>
+<function>FocusOut</function>.
</para>
+
<para>
-<!-- .LP -->
A widget can be insensitive because its <emphasis remap='I'>sensitive</emphasis> field is
<function>False</function>
or because one of its ancestors is insensitive and thus the widget's
<emphasis remap='I'>ancestor_sensitive</emphasis> field also is
-<function>False .</function>
+<function>False</function>.
A widget can but does not need to distinguish these two cases visually.
-<!-- .NT -->
Pop-up shells will have
<emphasis remap='I'>ancestor_sensitive</emphasis>
<function>False</function>
@@ -2978,26 +2565,21 @@ a resource specification of the form
in the application defaults resource file or to
otherwise ensure that the parent is
sensitive when creating pop-up shells.
-<!-- .NE -->
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To set the sensitivity state of a widget, use
-<function>XtSetSensitive .</function>
+<function>XtSetSensitive</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtSetSensitive" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtSetSensitive(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>sensitive</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>sensitive</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtSetSensitive'>
+<funcprototype>
+<funcdef>void <function>XtSetSensitive</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>Boolean <parameter>sensitive</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3005,7 +2587,7 @@ void XtSetSensitive(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>sensit
</term>
<listitem>
<para>
-Specifies the widget. (rI
+Specifies the widget. Must be of class RectObj or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -3022,8 +2604,6 @@ keyboard, pointer, and focus events.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtSetSensitive</function>
function first calls
@@ -3039,13 +2619,13 @@ recursively propagates the new value
down the child tree by calling
<function>XtSetValues</function>
on each child to set <emphasis remap='I'>ancestor_sensitive</emphasis> to
-<function>False .</function>
+<function>False</function>.
If <emphasis remap='I'>sensitive</emphasis> is
<function>True</function>
and the widget's class is a subclass of
Composite
and the widget's <emphasis remap='I'>ancestor_sensitive</emphasis> field is
-<function>True ,</function>
+<function>True</function>,
<function>XtSetSensitive</function>
sets the <emphasis remap='I'>ancestor_sensitive</emphasis> of each child to
<function>True</function>
@@ -3053,10 +2633,10 @@ and then recursively calls
<function>XtSetValues</function>
on each normal descendant that is now sensitive to set
<emphasis remap='I'>ancestor_sensitive</emphasis> to
-<function>True .</function>
+<function>True</function>.
</para>
+
<para>
-<!-- .LP -->
<function>XtSetSensitive</function>
calls
<function>XtSetValues</function>
@@ -3067,32 +2647,29 @@ the widget's set_values procedure should
take whatever display actions are needed
(for example, graying out or stippling the widget).
</para>
+
<para>
-<!-- .LP -->
<function>XtSetSensitive</function>
maintains the invariant that, if the parent has either <emphasis remap='I'>sensitive</emphasis>
or <emphasis remap='I'>ancestor_sensitive</emphasis>
-<function>False ,</function>
+<function>False</function>,
then all children have <emphasis remap='I'>ancestor_sensitive</emphasis>
-<function>False .</function>
-<!-- .sp -->
+<function>False</function>.
</para>
+
<para>
-<!-- .LP -->
To check the current sensitivity state of a widget,
use
-<function>XtIsSensitive .</function>
+<function>XtIsSensitive</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtIsSensitive" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-Boolean XtIsSensitive(<emphasis remap='I'>w</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtIsSensitive'>
+<funcprototype>
+<funcdef>Boolean <function>XtIsSensitive</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3100,14 +2677,12 @@ Boolean XtIsSensitive(<emphasis remap='I'>w</emphasis>)
</term>
<listitem>
<para>
-Specifies the object. (oI
+Specifies the object. Must be of class Object or any subclass thereof.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtIsSensitive</function>
function returns
@@ -3117,42 +2692,37 @@ or
to indicate whether user input events are being dispatched.
If object's class is a subclass of RectObj and
both <emphasis remap='I'>sensitive</emphasis> and <emphasis remap='I'>ancestor_sensitive</emphasis> are
-<function>True ,</function>
+<function>True</function>,
<function>XtIsSensitive</function>
returns
-<function>True ;</function>
+<function>True</function>;
otherwise, it returns
-<function>False .</function>
-
+<function>False</function>.
</para>
-</sect2>
-<sect2 id="Adding_Background_Work_Procedures">
+</sect1>
+
+<sect1 id="Adding_Background_Work_Procedures">
<title>Adding Background Work Procedures</title>
-<!-- .XS -->
-<!-- <function>(SN Adding Background Work Procedures</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-The (xI have some limited support for background processing.
+The Intrinsics have some limited support for background processing.
Because most applications spend most of their time waiting for input,
you can register an idle-time work procedure
that is called when the toolkit would otherwise block in
<function>XtAppNextEvent</function>
or
-<function>XtAppProcessEvent .</function>
+<function>XtAppProcessEvent</function>.
Work procedure pointers are of type
-<function>XtWorkProc .</function>
+<function>XtWorkProc</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtWorkProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef Boolean (*XtWorkProc)(XtPointer);
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtWorkProc'>
+<funcprototype>
+<funcdef>Boolean <function>*XtWorkProc</function></funcdef>
+
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3166,40 +2736,33 @@ Passes the client data specified when the work procedure was registered.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
This procedure should return
<function>True</function>
when it is done to indicate that it
should be removed.
If the procedure returns
-<function>False ,</function>
+<function>False</function>,
it will remain registered and called again when the
application is next idle.
Work procedures should be very judicious about how much they do.
If they run for more than a small part of a second,
interactive feel is likely to suffer.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To register a work procedure for a given application, use
-<function>XtAppAddWorkProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppAddWorkProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-XtWorkProcId XtAppAddWorkProc(<emphasis remap='I'>app_context</emphasis>, <emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .br -->
- XtWorkProc <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAppAddWorkProc</function>.
+</para>
+
+<funcsynopsis id='XtAppAddWorkProc'>
+<funcprototype>
+<funcdef>XtWorkProcId <function>XtAppAddWorkProc</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+ <paramdef>XtWorkProc <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3234,8 +2797,6 @@ when it is called.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAppAddWorkProc</function>
function adds the specified work procedure for the application identified
@@ -3245,26 +2806,23 @@ Multiple work procedures can be registered,
and the most recently added one is always the one that is called.
However, if a work procedure adds another work procedure,
the newly added one has lower priority than the current one.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To remove a work procedure, either return
<function>True</function>
from the procedure when it is called or use
<function>XtRemoveWorkProc</function>
outside of the procedure.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveWorkProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveWorkProc(<emphasis remap='I'>id</emphasis>)
-<!-- .br -->
- XtWorkProcId <emphasis remap='I'>id</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtRemoveWorkProc'>
+<funcprototype>
+<funcdef>void <function>XtRemoveWorkProc</function></funcdef>
+ <paramdef>XtWorkProcId <parameter>id</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3278,21 +2836,15 @@ Specifies which work procedure to remove.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveWorkProc</function>
function explicitly removes the specified background work procedure.
-
</para>
-</sect2>
-<sect2 id="X_Event_Filters">
+</sect1>
+
+<sect1 id="X_Event_Filters">
<title>X Event Filters</title>
-<!-- .XS -->
-<!-- (SN X Event Filters -->
-<!-- .XE -->
<para>
-<!-- .LP -->
The event manager provides filters that can be applied to
specific X events.
The filters, which screen out events that are redundant or are temporarily
@@ -3300,54 +2852,38 @@ unwanted, handle
pointer motion compression,
enter/leave compression, and
exposure compression.
-
</para>
-<sect3 id="Pointer_Motion_Compression">
+<sect2 id="Pointer_Motion_Compression">
<title>Pointer Motion Compression</title>
-<!-- .XS -->
-<!-- (SN Pointer Motion Compression -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Widgets can have a hard time keeping up with a rapid stream of
pointer motion events. Furthermore,
they usually do not care about every motion event. To throw out
redundant motion events, the widget class field <emphasis remap='I'>compress_motion</emphasis> should be
-<function>True .</function>
-<!-- .IN "compress_motion field" -->
+<function>True</function>.
When a request for an event would return a motion event,
-the (xI check if there are any other motion events
+the Intrinsics check if there are any other motion events
for the same widget immediately
following the current one and, if so, skip all but the last of them.
-
</para>
-</sect3>
-<sect3 id="Enter_Leave_Compression">
+</sect2>
+
+<sect2 id="Enter_Leave_Compression">
<title>Enter/Leave Compression</title>
-<!-- .XS -->
-<!-- (SN Enter/Leave Compression -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To throw out pairs of enter and leave events that have no intervening events,
as can happen when the user moves the pointer across a widget
without stopping in it,
the widget class field <emphasis remap='I'>compress_enterleave</emphasis> should be
-<function>True .</function>
-<!-- .IN "compress_enterleave field" -->
+<function>True</function>.
These enter and leave events are not delivered to the client
if they are found together in the input queue.
-
</para>
-</sect3>
-<sect3 id="Exposure_Compression">
+</sect2>
+
+<sect2 id="Exposure_Compression">
<title>Exposure Compression</title>
-<!-- .XS -->
-<!-- (SN Exposure Compression -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-<!-- .IN "compress_expose field" -->
Many widgets prefer to process a series of exposure events as a
single expose region rather than as individual rectangles. Widgets
with complex displays might use the expose region as a clip list
@@ -3356,41 +2892,36 @@ ignore the region entirely and redisplay their whole window or
might get the bounding box from the region and redisplay only that
rectangle.
</para>
+
<para>
-<!-- .LP -->
In either case, these widgets do not care about getting partial exposure events.
The <emphasis remap='I'>compress_exposure</emphasis> field in the widget class
structure specifies the type and number of exposure events that are
dispatched to the widget's expose procedure. This field must be
initialized to one of the following values:
-<!-- .sp -->
-<!-- .sM -->
+</para>
+
<literallayout class="monospaced">
-<!-- .TA 3i -->
-<!-- .ta 3i -->
#define XtExposeNoCompress ((XtEnum)False)
#define XtExposeCompressSeries ((XtEnum)True)
#define XtExposeCompressMultiple &lt;implementation-defined&gt;
#define XtExposeCompressMaximal &lt;implementation-defined&gt;
</literallayout>
-</para>
+
<para>
-<!-- .LP -->
-<!-- .eM -->
optionally ORed with any combination of the following flags (all with
implementation-defined values):
-<function>XtExposeGraphicsExpose ,</function>
-<function>XtExposeGraphicsExposeMerged ,</function>
-<function>XtExposeNoExpose ,</function>
+<function>XtExposeGraphicsExpose</function>,
+<function>XtExposeGraphicsExposeMerged</function>,
+<function>XtExposeNoExpose</function>,
and
-<function>XtExposeNoRegion .</function>
-
+<function>XtExposeNoRegion</function>.
</para>
+
<para>
-<!-- .LP -->
If the <emphasis remap='I'>compress_exposure</emphasis> field in the widget class structure does not
specify
-<function>XtExposeNoCompress ,</function>
+<function>XtExposeNoCompress</function>,
the event manager calls the widget's expose procedure only
once for a series of exposure events.
In this case, all
@@ -3405,17 +2936,15 @@ and calls the widget's expose procedure,
passing the modified exposure event and (unless
<function>XtExposeNoRegion</function>
is specified) the region.
-For more information on regions, see Section 16.5 in <emphasis remap='I'>(xL</emphasis>.)
+For more information on regions, see Section 16.5 in <emphasis remap='I'>Xlib — C Language X Interface.</emphasis>.)
</para>
+
<para>
-<!-- .LP -->
The values have the following interpretation:
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
<function>XtExposeNoCompress</function>
-<!-- .IN "XtExposeNoCompress" "" "@DEF@" -->
</para>
<itemizedlist>
<listitem>
@@ -3423,14 +2952,11 @@ The values have the following interpretation:
No exposure compression is performed; every selected event is
individually dispatched to the expose procedure with a <emphasis remap='I'>region</emphasis>
argument of NULL.
-<!-- .sp -->
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
<function>XtExposeCompressSeries</function>
-<!-- .IN "XtExposeCompressSeries" "" "@DEF@" -->
</para>
<itemizedlist>
<listitem>
@@ -3438,14 +2964,11 @@ argument of NULL.
Each series of exposure events is coalesced into a single event,
which is dispatched
when an exposure event with count equal to zero is reached.
-<!-- .sp -->
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
<function>XtExposeCompressMultiple</function>
-<!-- .IN "XtExposeCompressMultiple" "" "@DEF@" -->
</para>
<itemizedlist>
<listitem>
@@ -3455,14 +2978,11 @@ event, which is dispatched
when an exposure event with count equal to zero is reached and either
the event queue is empty or the next event is not an exposure event
for the same widget.
-<!-- .sp -->
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
<function>XtExposeCompressMaximal</function>
-<!-- .IN "XtExposeCompressMaximal" "" "@DEF" -->
</para>
<itemizedlist>
<listitem>
@@ -3470,21 +2990,17 @@ for the same widget.
All expose series currently in the queue for the widget
are coalesced into a single
event without regard to intervening nonexposure events. If a
-partial series is in the end of the queue, the (xI will
+partial series is in the end of the queue, the Intrinsics will
block until the end of the series is received.
-<!-- .sp -->
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
The additional flags have the following meaning:
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
<function>XtExposeGraphicsExpose</function>
-<!-- .IN "XtExposeGraphicsExpose" "" "@DEF@" -->
</para>
<itemizedlist>
<listitem>
@@ -3497,14 +3013,11 @@ the expose procedure.
events are compressed, if specified, in the same manner as
<function>Expose</function>
events.
-<!-- .sp -->
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
<function>XtExposeGraphicsExposeMerged</function>
-<!-- .IN "XtExposeGraphicsExposeMerged" "" "@DEF@" -->
</para>
<itemizedlist>
<listitem>
@@ -3522,15 +3035,12 @@ determining the type of the event passed to the expose procedure.
If this flag is not set, then only series of the same event type
as the event at the head of the queue are coalesced. This flag
also implies
-<function>XtExposeGraphicsExpose .</function>
-<!-- .sp -->
+<function>XtExposeGraphicsExpose</function>.
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
<function>XtExposeNoExpose</function>
-<!-- .IN "XtExposeNoExpose" "" "@DEF@" -->
</para>
<itemizedlist>
<listitem>
@@ -3541,14 +3051,11 @@ events are also to be dispatched to the expose procedure.
<function>NoExpose</function>
events are never coalesced with
other exposure events or with each other.
-<!-- .sp -->
</para>
</listitem>
</itemizedlist>
<para>
-<!-- .LP -->
<function>XtExposeNoRegion</function>
-<!-- .IN "XtExposeNoRegion" "" "@DEF" -->
</para>
<itemizedlist>
<listitem>
@@ -3558,51 +3065,38 @@ procedure is NULL. The rectangle in the event will still
contain bounding box information for the entire series of
compressed exposure events. This option saves processing time when the
region is not needed by the widget.
-
</para>
</listitem>
</itemizedlist>
-</sect3>
</sect2>
-<sect2 id="Widget_Exposure_and_Visibility">
+</sect1>
+
+<sect1 id="Widget_Exposure_and_Visibility">
<title>Widget Exposure and Visibility</title>
-<!-- .XS -->
-<!-- (SN Widget Exposure and Visibility -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Every primitive widget and some composite widgets display data on the screen
by means of direct Xlib calls.
Widgets cannot simply write to the screen and forget what they have done.
They must keep enough state to redisplay the window or parts
of it if a portion is obscured and then reexposed.
-
</para>
-<sect3 id="Redisplay_of_a_Widget_The_expose_Procedure">
+
+<sect2 id="Redisplay_of_a_Widget_The_expose_Procedure">
<title>Redisplay of a Widget: The expose Procedure</title>
-<!-- .XS -->
-<!-- (SN Redisplay of a Widget: The expose Procedure -->
-<!-- .XE -->
-<!-- .IN "expose procedure" -->
<para>
-<!-- .LP -->
The expose procedure pointer in a widget class is of type
-<function>XtExposeProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtExposeProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef void (*XtExposeProc)(Widget, XEvent*, Region);
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- XEvent *<emphasis remap='I'>event</emphasis>;
-<!-- .br -->
- Region <emphasis remap='I'>region</emphasis>;
-<!-- .FN -->
+<function>XtExposeProc</function>.
+</para>
+
+<funcsynopsis id='XtExposeProc'>
+<funcprototype>
+<funcdef>void <function>*XtExposeProc</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>XEvent *<parameter>event</parameter></paramdef>
+ <paramdef>Region <parameter>region</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3636,43 +3130,39 @@ Specifies the union of all rectangles in this exposure sequence.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The redisplay of a widget upon exposure is the responsibility of the
expose procedure in the widget's class record.
If a widget has no display semantics,
it can specify NULL for the <emphasis remap='I'>expose</emphasis> field.
Many composite widgets serve only as containers for their children
and have no expose procedure.
-<!-- .NT -->
If the <emphasis remap='I'>expose</emphasis> procedure is NULL,
<function>XtRealizeWidget</function>
fills in a default bit gravity of
<function>NorthWestGravity</function>
before it calls the widget's realize procedure.
-<!-- .NE -->
</para>
+
<para>
-<!-- .LP -->
If the widget's <emphasis remap='I'>compress_exposure</emphasis> class field specifies
<function>XtExposeNoCompress</function>
or
-<function>XtExposeNoRegion ,</function>
+<function>XtExposeNoRegion</function>,
or if the event type is
<function>NoExpose</function>
(see Section 7.9.3),
<emphasis remap='I'>region</emphasis> is NULL. If
<function>XtExposeNoCompress</function>
is not specified and the event type is not
-<function>NoExpose ,</function>
+<function>NoExpose</function>,
the event is the final event in the compressed series
but <emphasis remap='I'>x</emphasis>, <emphasis remap='I'>y</emphasis>, <emphasis remap='I'>width</emphasis>, and <emphasis remap='I'>height</emphasis> contain
the bounding box for all the compressed events.
-The region is created and destroyed by the (xI, but
+The region is created and destroyed by the Intrinsics, but
the widget is permitted to modify the region contents.
</para>
+
<para>
-<!-- .LP -->
A small simple widget (for example, Label) can ignore the bounding box
information in the event and redisplay the entire window.
A more complicated widget (for example, Text) can use the bounding box
@@ -3683,8 +3173,8 @@ The expose procedure is not chained and is therefore
responsible for exposure of all superclass data
as well as its own.
</para>
+
<para>
-<!-- .LP -->
However,
it often is possible to anticipate the display needs of several levels
of subclassing.
@@ -3693,43 +3183,37 @@ the widgets Label, Pushbutton, and Toggle,
you could write a single display routine in Label that uses display state
fields like
</para>
-<para>
-<!-- .LP -->
<literallayout class="monospaced">
Boolean invert;
Boolean highlight;
Dimension highlight_width;
</literallayout>
+<para>
Label would have <emphasis remap='I'>invert</emphasis> and <emphasis remap='I'>highlight</emphasis> always
<function>False</function>
and <emphasis remap='I'>highlight_width</emphasis> zero.
Pushbutton would dynamically set <emphasis remap='I'>highlight</emphasis> and <emphasis remap='I'>highlight_width</emphasis>,
but it would leave <emphasis remap='I'>invert</emphasis> always
-<function>False .</function>
+<function>False</function>.
Finally, Toggle would dynamically set all three.
In this case,
the expose procedures for Pushbutton and Toggle inherit
their superclass's expose procedure;
see Section 1.6.10.
-
</para>
-</sect3>
-<sect3 id="Widget_Visibility">
+</sect2>
+
+<sect2 id="Widget_Visibility">
<title>Widget Visibility</title>
-<!-- .XS -->
-<!-- (SN Widget Visibility -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Some widgets may use substantial computing resources to produce the
data they will display.
However, this effort is wasted if the widget is not actually visible
on the screen, that is, if the widget is obscured by another application
or is iconified.
</para>
+
<para>
-<!-- .LP -->
-<!-- .IN "Visibility" -->
The <emphasis remap='I'>visible</emphasis> field in the
core
widget structure provides a hint to the widget that it need not compute
@@ -3743,18 +3227,18 @@ but is
<function>False</function>
if the widget is fully obscured.
</para>
+
<para>
-<!-- .LP -->
Widgets can use or ignore the <emphasis remap='I'>visible</emphasis> hint.
If they ignore it,
they should have <emphasis remap='I'>visible_interest</emphasis> in their widget class record set
-<function>False .</function>
+<function>False</function>.
In such cases,
the <emphasis remap='I'>visible</emphasis> field is initialized
<function>True</function>
and never changes.
If <emphasis remap='I'>visible_interest</emphasis> is
-<function>True ,</function>
+<function>True</function>,
the event manager asks for
<function>VisibilityNotify</function>
events for the widget and sets <emphasis remap='I'>visible</emphasis> to
@@ -3763,46 +3247,37 @@ on
<function>VisibilityUnobscured</function>
or
<function>VisibilityPartiallyObscured</function>
-<!-- .IN VisibilityNotify -->
events and
<function>False</function>
on
<function>VisibilityFullyObscured</function>
events.
-
</para>
-</sect3>
</sect2>
-<sect2 id="X_Event_Handlers">
+</sect1>
+
+<sect1 id="X_Event_Handlers">
<title>X Event Handlers</title>
-<!-- .XS -->
-<!-- (SN X Event Handlers -->
-<!-- .XE -->
<para>
-<!-- .LP -->
Event handlers are procedures called when specified events
occur in a widget.
Most widgets need not use event handlers explicitly.
-Instead, they use the (xI translation manager.
+Instead, they use the Intrinsics translation manager.
Event handler procedure pointers are of the type
-<function>XtEventHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtEventHandler" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef void (*XtEventHandler)(Widget, XtPointer, XEvent*, Boolean*);
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- XEvent *<emphasis remap='I'>event</emphasis>;
-<!-- .br -->
- Boolean *<emphasis remap='I'>continue_to_dispatch</emphasis>;
-<!-- .FN -->
+<function>XtEventHandler</function>.
+</para>
+
+<funcsynopsis id='XtEventHandler'>
+<funcprototype>
+<funcdef>void <function>*XtEventHandler</function></funcdef>
+
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>XEvent *<parameter>event</parameter></paramdef>
+ <paramdef>Boolean *<parameter>continue_to_dispatch</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3848,11 +3323,9 @@ should be called.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
After receiving an event and before calling any event handlers, the
Boolean pointed to by <emphasis remap='I'>continue_to_dispatch</emphasis> is initialized to
-<function>True .</function>
+<function>True</function>.
When an event handler is called, it may decide that further processing
of the event is not desirable and may store
<function>False</function>
@@ -3860,44 +3333,32 @@ in this Boolean, in
which case any handlers remaining to be called for the event are
ignored.
</para>
+
<para>
-<!-- .LP -->
-The circumstances under which the (xI may add event handlers
+The circumstances under which the Intrinsics may add event handlers
to a widget are currently implementation-dependent. Clients must
therefore be aware that storing
<function>False</function>
into the <emphasis remap='I'>continue_to_dispatch</emphasis> argument can lead to portability problems.
-
</para>
-<sect3 id="Event_Handlers_That_Select_Events">
+<sect2 id="Event_Handlers_That_Select_Events">
<title>Event Handlers That Select Events</title>
-<!-- .XS -->
-<!-- (SN Event Handlers That Select Events -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To register an event handler procedure with the dispatch mechanism, use
-<function>XtAddEventHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAddEventHandler" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAddEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>nonmaskable</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- EventMask <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>nonmaskable</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAddEventHandler</function>.
+</para>
+
+<funcsynopsis id='XtAddEventHandler'>
+<funcprototype>
+<funcdef>void <function>XtAddEventHandler</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>EventMask <parameter>event_mask</parameter></paramdef>
+ <paramdef>Boolean <parameter>nonmaskable</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -3905,7 +3366,7 @@ void XtAddEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>eve
</term>
<listitem>
<para>
-Specifies the widget for which this event handler is being registered. (cI
+Specifies the widget for which this event handler is being registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -3927,12 +3388,12 @@ Specifies the event mask for which to call this procedure.
<para>
Specifies whether this procedure should be
called on the nonmaskable events
-<function>( GraphicsExpose ,</function>
-<function>NoExpose ,</function>
-<function>SelectionClear ,</function>
-<function>SelectionRequest ,</function>
-<function>SelectionNotify ,</function>
-<function>ClientMessage ,</function>
+<function>( GraphicsExpose</function>,
+<function>NoExpose</function>,
+<function>SelectionClear</function>,
+<function>SelectionRequest</function>,
+<function>SelectionNotify</function>,
+<function>ClientMessage</function>,
and
<function>MappingNotify ).</function>
</para>
@@ -3960,8 +3421,6 @@ Specifies additional data to be passed to the event handler.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAddEventHandler</function>
function registers a procedure with the dispatch mechanism that is
@@ -3976,36 +3435,28 @@ the specified mask augments the existing mask.
If the widget is realized,
<function>XtAddEventHandler</function>
calls
-<function>XSelectInput ,</function>
+<function>XSelectInput</function>,
if necessary.
The order in which this procedure is called relative to other handlers
registered for the same event is not defined.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To remove a previously registered event handler, use
-<function>XtRemoveEventHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveEventHandler" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>nonmaskable</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- EventMask <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>nonmaskable</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtRemoveEventHandler</function>.
+</para>
+
+<funcsynopsis id='XtRemoveEventHandler'>
+<funcprototype>
+<funcdef>void <function>XtRemoveEventHandler</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>EventMask <parameter>event_mask</parameter></paramdef>
+ <paramdef>Boolean <parameter>nonmaskable</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4013,7 +3464,7 @@ void XtRemoveEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>
</term>
<listitem>
<para>
-Specifies the widget for which this procedure is registered. (cI
+Specifies the widget for which this procedure is registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4035,12 +3486,12 @@ Specifies the event mask for which to unregister this procedure.
<para>
Specifies whether this procedure should be
removed on the nonmaskable events
-<function>( GraphicsExpose ,</function>
-<function>NoExpose ,</function>
-<function>SelectionClear ,</function>
-<function>SelectionRequest ,</function>
-<function>SelectionNotify ,</function>
-<function>ClientMessage ,</function>
+<function>( GraphicsExpose</function>,
+<function>NoExpose</function>,
+<function>SelectionClear</function>,
+<function>SelectionRequest</function>,
+<function>SelectionNotify</function>,
+<function>ClientMessage</function>,
and
<function>MappingNotify ).</function>
</para>
@@ -4068,8 +3519,6 @@ Specifies the registered client data.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveEventHandler</function>
function unregisters an event handler registered with
@@ -4082,14 +3531,14 @@ when the handler was registered.
If the widget is realized and no other event handler requires the event,
<function>XtRemoveEventHandler</function>
calls
-<function>XSelectInput .</function>
+<function>XSelectInput</function>.
If the specified procedure has not been registered
or if it has been registered with a different value of <emphasis remap='I'>client_data</emphasis>,
<function>XtRemoveEventHandler</function>
returns without reporting an error.
</para>
+
<para>
-<!-- .LP -->
To stop a procedure registered with
<function>XtAddEventHandler</function>
or
@@ -4099,48 +3548,35 @@ from receiving all selected events, call
with an <emphasis remap='I'>event_mask</emphasis> of
<function>XtAllEvents</function>
and <emphasis remap='I'>nonmaskable</emphasis>
-<function>True .</function>
+<function>True</function>.
The procedure will continue to receive any events
that have been specified in calls to
<function>XtAddRawEventHandler</function>
or
-<function>XtInsertRawEventHandler .</function>
-<!-- .sp -->
+<function>XtInsertRawEventHandler</function>.
</para>
+
<para>
-<!-- .LP -->
To register an event handler procedure that receives events before or
after all previously registered event handlers, use
-<function>XtInsertEventHandler .</function>
+<function>XtInsertEventHandler</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtListPosition" "" "@DEF@" -->
-<!-- .IN "XtInsertEventHandler" "" "@DEF@" -->
-<!-- .sM -->
<literallayout class="monospaced">
typedef enum {XtListHead, XtListTail} XtListPosition;
</literallayout>
-</para>
-<para>
-<!-- .LP -->
-</para>
-<!-- .FD 0 -->
-void XtInsertEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>nonmaskable</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>, <emphasis remap='I'>position</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- EventMask <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>nonmaskable</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- XtListPosition <emphasis remap='I'>position</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtInsertEventHandler'>
+<funcprototype>
+<funcdef> <function>XtInsertEventHandler</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>EventMask <parameter>event_mask</parameter></paramdef>
+ <paramdef>Boolean <parameter>nonmaskable</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>XtListPosition <parameter>position</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4148,7 +3584,7 @@ void XtInsertEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>
</term>
<listitem>
<para>
-Specifies the widget for which this event handler is being registered. (cI
+Specifies the widget for which this event handler is being registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4170,12 +3606,12 @@ Specifies the event mask for which to call this procedure.
<para>
Specifies whether this procedure should be
called on the nonmaskable events
-<function>( GraphicsExpose ,</function>
-<function>NoExpose ,</function>
-<function>SelectionClear ,</function>
-<function>SelectionRequest ,</function>
-<function>SelectionNotify ,</function>
-<function>ClientMessage ,</function>
+<function>( GraphicsExpose</function>,
+<function>NoExpose</function>,
+<function>SelectionClear</function>,
+<function>SelectionRequest</function>,
+<function>SelectionNotify</function>,
+<function>ClientMessage</function>,
and
<function>MappingNotify ).</function>
</para>
@@ -4214,59 +3650,46 @@ relative to other previously registered handlers.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtInsertEventHandler</function>
is identical to
<function>XtAddEventHandler</function>
with the additional <emphasis remap='I'>position</emphasis> argument. If <emphasis remap='I'>position</emphasis> is
-<function>XtListHead ,</function>
+<function>XtListHead</function>,
the event
handler is registered so that it is called before any event
handlers that were previously registered for the same widget. If
<emphasis remap='I'>position</emphasis> is
-<function>XtListTail ,</function>
+<function>XtListTail</function>,
the event handler is registered to be called
after any previously registered event handlers. If the procedure is
already registered with the same <emphasis remap='I'>client_data</emphasis> value, the specified mask
augments the existing mask and the procedure is repositioned in
the list.
-
</para>
-</sect3>
-<sect3 id="Event_Handlers_That_Do_Not_Select_Events">
+</sect2>
+
+<sect2 id="Event_Handlers_That_Do_Not_Select_Events">
<title>Event Handlers That Do Not Select Events</title>
-<!-- .XS -->
-<!-- (SN Event Handlers That Do Not Select Events -->
-<!-- .XE -->
<para>
-<!-- .LP -->
On occasion,
clients need to register an event handler procedure with the
dispatch mechanism without explicitly
causing the X server to select for that event.
To do this, use
-<function>XtAddRawEventHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAddRawEventHandler" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAddRawEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>nonmaskable</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- EventMask <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>nonmaskable</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtAddRawEventHandler</function>.
+</para>
+
+<funcsynopsis id='XtAddRawEventHandler'>
+<funcprototype>
+<funcdef>void <function>XtAddRawEventHandler</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>EventMask <parameter>event_mask</parameter></paramdef>
+ <paramdef>Boolean <parameter>nonmaskable</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4274,7 +3697,7 @@ void XtAddRawEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>
</term>
<listitem>
<para>
-Specifies the widget for which this event handler is being registered. (cI
+Specifies the widget for which this event handler is being registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4296,12 +3719,12 @@ Specifies the event mask for which to call this procedure.
<para>
Specifies whether this procedure should be
called on the nonmaskable events
-<function>( GraphicsExpose ,</function>
-<function>NoExpose ,</function>
-<function>SelectionClear ,</function>
-<function>SelectionRequest ,</function>
-<function>SelectionNotify ,</function>
-<function>ClientMessage ,</function>
+<function>( GraphicsExpose</function>,
+<function>NoExpose</function>,
+<function>SelectionClear</function>,
+<function>SelectionRequest</function>,
+<function>SelectionNotify</function>,
+<function>ClientMessage</function>,
and
<function>MappingNotify ).</function>
</para>
@@ -4329,8 +3752,6 @@ Specifies additional data to be passed to the client's event handler.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtAddRawEventHandler</function>
function is similar to
@@ -4344,32 +3765,24 @@ If the procedure is already registered with the same <emphasis remap='I'>client_
the specified mask augments the existing mask.
The order in which this procedure is called relative to other handlers
registered for the same event is not defined.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To remove a previously registered raw event handler, use
-<function>XtRemoveRawEventHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveRawEventHandler" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveRawEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>nonmaskable</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- EventMask <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>nonmaskable</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtRemoveRawEventHandler</function>.
+</para>
+
+<funcsynopsis id='XtRemoveRawEventHandler'>
+<funcprototype>
+<funcdef>void <function>XtRemoveRawEventHandler</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>EventMask <parameter>event_mask</parameter></paramdef>
+ <paramdef>Boolean <parameter>nonmaskable</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4377,7 +3790,7 @@ void XtRemoveRawEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='
</term>
<listitem>
<para>
-Specifies the widget for which this procedure is registered. (cI
+Specifies the widget for which this procedure is registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4399,12 +3812,12 @@ Specifies the event mask for which to unregister this procedure.
<para>
Specifies whether this procedure should be
removed on the nonmaskable events
-<function>( GraphicsExpose ,</function>
-<function>NoExpose ,</function>
-<function>SelectionClear ,</function>
-<function>SelectionRequest ,</function>
-<function>SelectionNotify ,</function>
-<function>ClientMessage ,</function>
+<function>( GraphicsExpose</function>,
+<function>NoExpose</function>,
+<function>SelectionClear</function>,
+<function>SelectionRequest</function>,
+<function>SelectionNotify</function>,
+<function>ClientMessage</function>,
and
<function>MappingNotify ).</function>
</para>
@@ -4432,8 +3845,6 @@ Specifies the registered client data.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveRawEventHandler</function>
function unregisters an event handler registered with
@@ -4449,8 +3860,8 @@ or if it has been registered with a different value of <emphasis remap='I'>clien
<function>XtRemoveRawEventHandler</function>
returns without reporting an error.
</para>
+
<para>
-<!-- .LP -->
To stop a procedure
registered with
<function>XtAddRawEventHandler</function>
@@ -4461,42 +3872,33 @@ from receiving all nonselected events, call
with an <emphasis remap='I'>event_mask</emphasis> of
<function>XtAllEvents</function>
and <emphasis remap='I'>nonmaskable</emphasis>
-<function>True .</function>
+<function>True</function>.
The procedure
will continue to receive any events that have been specified in calls to
<function>XtAddEventHandler</function>
or
-<function>XtInsertEventHandler .</function>
-<!-- .sp -->
+<function>XtInsertEventHandler</function>.
</para>
+
<para>
-<!-- .LP -->
To register an event handler procedure that receives events before or
after all previously registered event handlers without selecting for
the events, use
-<function>XtInsertRawEventHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtInsertRawEventHandler" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtInsertRawEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='I'>event_mask</emphasis>, <emphasis remap='I'>nonmaskable</emphasis>, \
-<emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>, <emphasis remap='I'>position</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .br -->
- EventMask <emphasis remap='I'>event_mask</emphasis>;
-<!-- .br -->
- Boolean <emphasis remap='I'>nonmaskable</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- XtListPosition <emphasis remap='I'>position</emphasis>;
-<!-- .FN -->
+<function>XtInsertRawEventHandler</function>.
+</para>
+
+<funcsynopsis id='XtInsertRawEventHandler'>
+<funcprototype>
+<funcdef>void <function>XtInsertRawEventHandler</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+ <paramdef>EventMask <parameter>event_mask</parameter></paramdef>
+ <paramdef>Boolean <parameter>nonmaskable</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>XtListPosition <parameter>position</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4504,7 +3906,7 @@ void XtInsertRawEventHandler(<emphasis remap='I'>w</emphasis>, <emphasis remap='
</term>
<listitem>
<para>
-Specifies the widget for which this event handler is being registered. (cI
+Specifies the widget for which this event handler is being registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4526,12 +3928,12 @@ Specifies the event mask for which to call this procedure.
<para>
Specifies whether this procedure should be
called on the nonmaskable events
-<function>( GraphicsExpose ,</function>
-<function>NoExpose ,</function>
-<function>SelectionClear ,</function>
-<function>SelectionRequest ,</function>
-<function>SelectionNotify ,</function>
-<function>ClientMessage ,</function>
+<function>( GraphicsExpose</function>,
+<function>NoExpose</function>,
+<function>SelectionClear</function>,
+<function>SelectionRequest</function>,
+<function>SelectionNotify</function>,
+<function>ClientMessage</function>,
and
<function>MappingNotify ).</function>
</para>
@@ -4570,8 +3972,6 @@ relative to other previously registered handlers.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtInsertRawEventHandler</function>
function is similar to
@@ -4584,29 +3984,23 @@ the procedure is already registered with the same <emphasis remap='I'>client_dat
value, the
specified mask augments the existing mask and the procedure is
repositioned in the list.
-
</para>
-</sect3>
-<sect3 id="Current_Event_Mask">
+</sect2>
+
+<sect2 id="Current_Event_Mask">
<title>Current Event Mask</title>
-<!-- .XS -->
-<!-- (SN Current Event Mask -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To retrieve the event mask for a given widget, use
-<function>XtBuildEventMask .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtBuildEventMask" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtBuildEventMask</function>.
</para>
-<!-- .FD 0 -->
-EventMask XtBuildEventMask(<emphasis remap='I'>w</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>w</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtBuildEventMask'>
+<funcprototype>
+<funcdef>EventMask <function>XtBuildEventMask</function></funcdef>
+ <paramdef>Widget <parameter>w</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4614,14 +4008,12 @@ EventMask XtBuildEventMask(<emphasis remap='I'>w</emphasis>)
</term>
<listitem>
<para>
-Specifies the widget. (cI
+Specifies the widget. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtBuildEventMask</function>
function returns the event mask representing the logical OR
@@ -4637,41 +4029,29 @@ structure by
<function>XtRealizeWidget</function>
and sent to the server when event handlers and translations are installed or
removed on the realized widget.
-
</para>
-</sect3>
-<sect3 id="Event_Handlers_for_X_Protocol_Extensions">
+</sect2>
+
+<sect2 id="Event_Handlers_for_X_Protocol_Extensions">
<title>Event Handlers for X11 Protocol Extensions</title>
-<!-- .XS -->
-<!-- <function>(SN Event Handlers for X11 Protocol Extensions</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-To register an event handler procedure with the (xI dispatch
+To register an event handler procedure with the Intrinsics dispatch
mechanism according to an event type, use
-<function>XtInsertEventTypeHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtInsertEventTypeHandler" "" "@DEF" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtInsertEventTypeHandler(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>event_type</emphasis>, \
-<emphasis remap='I'>select_data</emphasis>, <emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>, <emphasis remap='I'>position</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>event_type</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>select_data</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .br -->
- XtListPosition <emphasis remap='I'>position</emphasis>;
-<!-- .FN -->
+<function>XtInsertEventTypeHandler</function>.
+</para>
+
+<funcsynopsis id='XtInsertEventTypeHandler'>
+<funcprototype>
+<funcdef>void <function>XtInsertEventTypeHandler</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>int <parameter>event_type</parameter></paramdef>
+ <paramdef>XtPointer <parameter>select_data</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+ <paramdef>XtListPosition <parameter>position</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4679,7 +4059,7 @@ void XtInsertEventTypeHandler(<emphasis remap='I'>widget</emphasis>, <emphasis r
</term>
<listitem>
<para>
-Specifies the widget for which this event handler is being registered. (cI
+Specifies the widget for which this event handler is being registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4737,22 +4117,20 @@ previously registered handlers.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtInsertEventTypeHandler</function>
registers a procedure with the
dispatch mechanism that is to be called when an event that matches the
specified <emphasis remap='I'>event_type</emphasis> is dispatched to the specified <emphasis remap='I'>widget</emphasis>.
</para>
+
<para>
-<!-- .LP -->
If <emphasis remap='I'>event_type</emphasis> specifies one of the core X protocol events, then
<emphasis remap='I'>select_data</emphasis> must be a pointer to a value of type
-<function>EventMask ,</function>
+<function>EventMask</function>,
indicating
the event mask to be used to select for the desired event. This event
mask is included in the value returned by
-<function>XtBuildEventMask .</function>
+<function>XtBuildEventMask</function>.
If the widget is realized,
<function>XtInsertEventTypeHandler</function>
calls
@@ -4763,67 +4141,59 @@ to the
<function>XtInsertRawEventHandler</function>
function.
</para>
+
<para>
-<!-- .LP -->
If <emphasis remap='I'>event_type</emphasis> specifies an extension event type, then the semantics of
the data pointed to by <emphasis remap='I'>select_data</emphasis> are defined by the extension
selector registered for the specified event type.
</para>
+
<para>
-<!-- .LP -->
-In either case the (xI are not required to copy the data
+In either case the Intrinsics are not required to copy the data
pointed to by <emphasis remap='I'>select_data</emphasis>, so the caller must ensure that it remains
valid as long as the event handler remains registered with this value
of <emphasis remap='I'>select_data</emphasis>.
</para>
+
<para>
-<!-- .LP -->
The <emphasis remap='I'>position</emphasis> argument allows the client to control the order of
invocation of event handlers registered for the same event type. If
the client does not care about the order, it should normally specify
-<function>XtListTail ,</function>
+<function>XtListTail</function>,
which registers this event handler after any previously
registered handlers for this event type.
</para>
+
<para>
-<!-- .LP -->
Each widget has a single registered event handler list, which will
contain any procedure/client_data pair exactly once if it is
registered with
-<function>XtInsertEventTypeHandler ,</function>
+<function>XtInsertEventTypeHandler</function>,
regardless of the manner
in which it is registered and regardless of the value(s)
of <emphasis remap='I'>select_data</emphasis>. If the procedure is already registered with the
same <emphasis remap='I'>client_data</emphasis> value, the specified mask augments the existing
mask and the procedure is repositioned in the list.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To remove an event handler registered with
-<function>XtInsertEventTypeHandler ,</function>
+<function>XtInsertEventTypeHandler</function>,
use
-<function>XtRemoveEventTypeHandler .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRemoveEventTypeHandler" "" "@DEF" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRemoveEventTypeHandler(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>event_type</emphasis>, \
-<emphasis remap='I'>select_data</emphasis>, <emphasis remap='I'>proc</emphasis>, <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>event_type</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>select_data</emphasis>;
-<!-- .br -->
- XtEventHandler <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtRemoveEventTypeHandler</function>.
+</para>
+
+<funcsynopsis id='XtRemoveEventTypeHandler'>
+<funcprototype>
+<funcdef>void <function>XtRemoveEventTypeHandler</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>int <parameter>event_type</parameter></paramdef>
+ <paramdef>XtPointer <parameter>select_data</parameter></paramdef>
+ <paramdef>XtEventHandler <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4831,7 +4201,7 @@ void XtRemoveEventTypeHandler(<emphasis remap='I'>widget</emphasis>, <emphasis r
</term>
<listitem>
<para>
-Specifies the widget for which the event handler was registered. (cI
+Specifies the widget for which the event handler was registered. Must be of class Core or any subclass thereof.
</para>
</listitem>
</varlistentry>
@@ -4878,8 +4248,6 @@ Specifies the additional client data with which the procedure was registered.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRemoveEventTypeHandler</function>
function unregisters an event handler
@@ -4889,8 +4257,8 @@ for the specified event type.
The request is ignored if <emphasis remap='I'>client_data</emphasis> does not match the value given
when the handler was registered.
</para>
+
<para>
-<!-- .LP -->
If <emphasis remap='I'>event_type</emphasis> specifies one of the core X protocol events,
<emphasis remap='I'>select_data</emphasis> must be a pointer to a value of type
<function>EventMask, indicating the event</function>
@@ -4905,38 +4273,29 @@ to an event mask containing 0. This is similar to the
<function>XtRemoveRawEventHandler</function>
function.
</para>
+
<para>
-<!-- .LP -->
If <emphasis remap='I'>event_type</emphasis> specifies an extension event type, then the semantics of
the data pointed to by <emphasis remap='I'>select_data</emphasis> are defined by the extension
selector registered for the specified event type.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To register a procedure to select extension events for a widget, use
-<function>XtRegisterExtensionSelector .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtRegisterExtensionSelector" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtRegisterExtensionSelector(<emphasis remap='I'>display</emphasis>, <emphasis remap='I'>min_event_type</emphasis>, \
-<emphasis remap='I'>max_event_type</emphasis>, <emphasis remap='I'>proc</emphasis>,
- <emphasis remap='I'>client_data</emphasis>)
-<!-- .br -->
- Display <emphasis remap='I'>*display</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>min_event_type</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>max_event_type</emphasis>;
-<!-- .br -->
- XtExtensionSelectProc <emphasis remap='I'>proc</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtRegisterExtensionSelector</function>.
+</para>
+
+<funcsynopsis id='XtRegisterExtensionSelector'>
+<funcprototype>
+<funcdef>void <function>XtRegisterExtensionSelector</function></funcdef>
+ <paramdef>Display <parameter>*display</parameter></paramdef>
+ <paramdef>int <parameter>min_event_type</parameter></paramdef>
+ <paramdef>int <parameter>max_event_type</parameter></paramdef>
+ <paramdef>XtExtensionSelectProc <parameter>proc</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -4953,8 +4312,7 @@ Specifies the display for which the extension selector is to be registered.
<emphasis remap='I'>min_event_type</emphasis>
</term>
<listitem>
- <para>
- </para>
+ <para></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -4989,15 +4347,13 @@ Specifies additional data to be passed to the extension selector.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtRegisterExtensionSelector</function>
function registers a procedure to arrange
for the delivery of extension events to widgets.
</para>
+
<para>
-<!-- .LP -->
If <emphasis remap='I'>min_event_type</emphasis> and <emphasis remap='I'>max_event_type</emphasis> match the parameters
to a previous call to
<function>XtRegisterExtensionSelector</function>
@@ -5007,46 +4363,39 @@ registered values. If the range specified by <emphasis remap='I'>min_event_type
and <emphasis remap='I'>max_event_type</emphasis> overlaps the range of the parameters to a
previous call for the same display in any other way, an error results.
</para>
+
<para>
-<!-- .LP -->
When a widget is realized,
after the <emphasis remap='I'>core.realize</emphasis> method is called,
-the (xI check to see if any event
+the Intrinsics check to see if any event
handler specifies an event type within the range of a registered
-extension selector. If so, the (xI call each such selector.
-If an event type handler is added or removed, the (xI check to
+extension selector. If so, the Intrinsics call each such selector.
+If an event type handler is added or removed, the Intrinsics check to
see if the event type falls within the range of a registered extension
-selector, and if it does, calls the selector. In either case the (xI
+selector, and if it does, calls the selector. In either case the Intrinsics
pass a list of all the widget's event types that are within the
selector's range. The corresponding select data are also passed. The
selector is responsible for enabling the delivery of extension events
required by the widget.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
An extension selector is of type
-<function>XtExtensionSelectProc .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtExtensionSelectProc" "" "@DEF" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef void (*XtExtensionSelectProc)(Widget, int *, XtPointer *, int, \
-XtPointer);
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- int *<emphasis remap='I'>event_types</emphasis>;
-<!-- .br -->
- XtPointer *<emphasis remap='I'>select_data</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>count</emphasis>;
-<!-- .br -->
- XtPointer <emphasis remap='I'>client_data</emphasis>;
-<!-- .FN -->
+<function>XtExtensionSelectProc</function>.
+</para>
+
+<funcsynopsis id='XtExtensionSelectProc'>
+<funcprototype>
+<funcdef>void <function>*XtExtensionSelectProc</function></funcdef>
+
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>int *<parameter>event_types</parameter></paramdef>
+ <paramdef>XtPointer *<parameter>select_data</parameter></paramdef>
+ <paramdef>int <parameter>count</parameter></paramdef>
+ <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5077,7 +4426,7 @@ registered event handlers for.
<listitem>
<para>
Specifies a list of the select_data parameters specified in
-<function>XtInsertEventTypeHandler .</function>
+<function>XtInsertEventTypeHandler</function>.
</para>
</listitem>
</varlistentry>
@@ -5104,36 +4453,28 @@ Specifies the additional client data with which the procedure was registered.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The <emphasis remap='I'>event_types</emphasis> and <emphasis remap='I'>select_data</emphasis> lists will always have the
same number of elements, specified by <emphasis remap='I'>count</emphasis>.
Each event type/select data pair represents one call to
-<function>XtInsertEventTypeHandler .</function>
-<!-- .sp -->
+<function>XtInsertEventTypeHandler</function>.
</para>
+
<para>
-<!-- .LP -->
To register a procedure to dispatch events of a specific type within
-<function>XtDispatchEvent ,</function>
+<function>XtDispatchEvent</function>,
use
-<function>XtSetEventDispatcher .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtSetEventDispatcher" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-XtEventDispatchProc XtSetEventDispatcher(<emphasis remap='I'>display</emphasis>, <emphasis remap='I'>event_type</emphasis>, \
-<emphasis remap='I'>proc</emphasis>)
-<!-- .br -->
- Display *<emphasis remap='I'>display</emphasis>;
-<!-- .br -->
- int <emphasis remap='I'>event_type</emphasis>;
-<!-- .br -->
- XtEventDispatchProc <emphasis remap='I'>proc</emphasis>;
-<!-- .FN -->
+<function>XtSetEventDispatcher</function>.
+</para>
+
+<funcsynopsis id='XtSetEventDispatcher'>
+<funcprototype>
+<funcdef>XtEventDispatchProc <function>XtSetEventDispatcher</function></funcdef>
+ <paramdef>Display *<parameter>display</parameter></paramdef>
+ <paramdef>int <parameter>event_type</parameter></paramdef>
+ <paramdef>XtEventDispatchProc <parameter>proc</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5167,8 +4508,6 @@ Specifies the event dispatcher procedure.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtSetEventDispatcher</function>
function registers the event dispatcher procedure specified by <emphasis remap='I'>proc</emphasis>
@@ -5177,36 +4516,33 @@ dispatcher (or the default dispatcher if there was no previously registered
dispatcher) is returned. If <emphasis remap='I'>proc</emphasis> is NULL, the default procedure is
restored for the specified type.
</para>
+
<para>
-<!-- .LP -->
In the future, when
<function>XtDispatchEvent</function>
is called with an event type of <emphasis remap='I'>event_type</emphasis>, the specified <emphasis remap='I'>proc</emphasis>
(or the default dispatcher) is invoked to determine a widget
to which to dispatch the event.
</para>
+
<para>
-<!-- .LP -->
-The default dispatcher handles the (xI modal cascade and keyboard
+The default dispatcher handles the Intrinsics modal cascade and keyboard
focus mechanisms, handles the semantics of <emphasis remap='I'>compress_enterleave</emphasis>
and <emphasis remap='I'>compress_motion</emphasis>, and discards all extension events.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
An event dispatcher procedure pointer is of type
-<function>XtEventDispatchProc .</function>
+<function>XtEventDispatchProc</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtEventDispatchProc" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-typedef Boolean (*XtEventDispatchProc)(XEvent*)
-<!-- .br -->
- XEvent *<emphasis remap='I'>event</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtEventDispatchProc'>
+<funcprototype>
+<funcdef>Boolean <function>*XtEventDispatchProc</function></funcdef>
+ <paramdef>XEvent *<parameter>event</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5220,13 +4556,11 @@ Passes the event to be dispatched.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The event dispatcher procedure should determine whether this event is of
a type that should be dispatched to a widget.
</para>
+
<para>
-<!-- .LP -->
If the event should be dispatched to a widget, the event dispatcher
procedure should determine the appropriate widget to receive the
event, call
@@ -5236,9 +4570,9 @@ with the window of this widget, or
if the event is to be discarded, and if
<function>XFilterEvent</function>
returns
-<function>False ,</function>
+<function>False</function>,
dispatch the event to the widget using
-<function>XtDispatchEventToWidget .</function>
+<function>XtDispatchEventToWidget</function>.
The procedure should return
<function>True</function>
if either
@@ -5251,8 +4585,8 @@ and
<function>False</function>
otherwise.
</para>
+
<para>
-<!-- .LP -->
If the event should not be dispatched to a widget, the event
dispatcher procedure should attempt to dispatch the event elsewhere as
appropriate and return
@@ -5260,25 +4594,22 @@ appropriate and return
if it successfully dispatched the event and
<function>False</function>
otherwise.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
Some dispatchers for extension events may wish to forward events
according to the Intrinsics' keyboard focus mechanism. To determine
which widget is the end result of keyboard event forwarding, use
-<function>XtGetKeyboardFocusWidget .</function>
+<function>XtGetKeyboardFocusWidget</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtGetKeyboardFocusWidget" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-Widget XtGetKeyboardFocusWidget(<emphasis remap='I'>widget</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtGetKeyboardFocusWidget'>
+<funcprototype>
+<funcdef>Widget <function>XtGetKeyboardFocusWidget</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5292,31 +4623,25 @@ Specifies the widget to get forwarding information for.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtGetKeyboardFocusWidget</function>
function returns the widget that would be the end result of keyboard
event forwarding for a keyboard event for the specified widget.
-<!-- .sp -->
</para>
+
<para>
-<!-- .LP -->
To dispatch an event to a specified widget, use
-<function>XtDispatchEventToWidget .</function>
+<function>XtDispatchEventToWidget</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtDispatchEventToWidget" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-Boolean XtDispatchEventToWidget(<emphasis remap='I'>widget</emphasis>, <emphasis remap='I'>event</emphasis>)
-<!-- .br -->
- Widget <emphasis remap='I'>widget</emphasis>;
-<!-- .br -->
- XEvent *<emphasis remap='I'>event</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtDispatchEventToWidget'>
+<funcprototype>
+<funcdef>Boolean <function>XtDispatchEventToWidget</function></funcdef>
+ <paramdef>Widget <parameter>widget</parameter></paramdef>
+ <paramdef>XEvent *<parameter>event</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5340,154 +4665,124 @@ Specifies a pointer to the event to be dispatched.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
The
<function>XtDispatchEventToWidget</function>
function scans the list of registered event handlers for the
specified widget and calls each handler that has been registered
for the specified event type, subject to the <emphasis remap='I'>continue_to_dispatch</emphasis>
value returned by each handler.
-The (xI behave as if event handlers were registered at the head
+The Intrinsics behave as if event handlers were registered at the head
of the list for
-<function>Expose ,</function>
-<function>NoExpose ,</function>
-<function>GraphicsExpose ,</function>
+<function>Expose</function>,
+<function>NoExpose</function>,
+<function>GraphicsExpose</function>,
and
<function>VisibilityNotify</function>
events to invoke the widget's expose procedure according to the exposure
compression rules and to update the widget's <emphasis remap='I'>visible</emphasis> field
if <emphasis remap='I'>visible_interest</emphasis> is
-<function>True .</function>
+<function>True</function>.
These internal event handlers never set <emphasis remap='I'>continue_to_dispatch</emphasis> to
-<function>False .</function>
+<function>False</function>.
</para>
+
<para>
-<!-- .LP -->
<function>XtDispatchEventToWidget</function>
returns
<function>True</function>
if any event handler was called and
<function>False</function>
otherwise.
-
</para>
-</sect3>
</sect2>
-<sect2 id="Using_the_xI_in_a_Multi_Threaded_Environment">
-<title>Using the (xI in a Multi-Threaded Environment</title>
-<!-- .XS -->
-<!-- (SN Using the (xI in a Multi-Threaded Environment -->
-<!-- .XE -->
-<para>
-<!-- .LP -->
-The (xI may be used in environments that offer multiple threads
+</sect1>
+
+<sect1 id="Using_the_xI_in_a_Multi_Threaded_Environment">
+<title>Using the Intrinsics in a Multi-Threaded Environment</title>
+<para>
+The Intrinsics may be used in environments that offer multiple threads
of execution within the context of a single process. A multi-threaded
-application using the (xI must explicitly initialize the toolkit
+application using the Intrinsics must explicitly initialize the toolkit
for mutually exclusive access by calling
-<function>XtToolkitThreadInitialize .</function>
-
+<function>XtToolkitThreadInitialize</function>.
</para>
-<sect3 id="Initializing_a_Multi_Threaded_xI_Application">
-<title>Initializing a Multi-Threaded (xI Application</title>
-<!-- .XS -->
-<!-- <function>(SN Initializing a Multi-Threaded (xI Application</function> -->
-<!-- .XE -->
+<sect2 id="Initializing_a_Multi_Threaded_xI_Application">
+<title>Initializing a Multi-Threaded Intrinsics Application</title>
<para>
-<!-- .LP -->
-To test and initialize (xI support for mutually exclusive thread
+To test and initialize Intrinsics support for mutually exclusive thread
access, call
-<function>XtToolkitThreadInitialize .</function>
+<function>XtToolkitThreadInitialize</function>.
</para>
+
+<funcsynopsis id='XtToolkitThreadInitialize'>
+<funcprototype>
+<funcdef>Boolean <function>XtToolkitThreadInitialize</function></funcdef>
+ <paramdef><parameter></parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<para>
-<!-- .LP -->
-<!-- .IN "XtToolkitThreadInitialize" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-Boolean XtToolkitThreadInitialize()
-<!-- .FN -->
-<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtToolkitThreadInitialize</function>
-returns <function>True</function> if the (xI support mutually exclusive thread
+returns <function>True</function> if the Intrinsics support mutually exclusive thread
access, otherwise it returns <function>False</function>. <function>XtToolkitThreadInitialize</function>
must be called before
-<function>XtCreateApplicationContext ,</function>
-<function>XtAppInitialize ,</function>
-<function>XtOpenApplication ,</function>
+<function>XtCreateApplicationContext</function>,
+<function>XtAppInitialize</function>,
+<function>XtOpenApplication</function>,
or
<function>XtSetLanguageProc</function>
is called. <function>XtToolkitThreadInitialize</function> may be called more than once;
however, the application writer must ensure that it is not called
simultaneously by two or more threads.
-
</para>
-</sect3>
-<sect3 id="Locking_tk_Data_Structures">
+</sect2>
+
+<sect2 id="Locking_tk_Data_Structures">
<title>Locking (tk Data Structures</title>
-<!-- .XS -->
-<!-- <function>(SN Locking (tk Data Structures</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
-The (xI employs two levels of locking: application context and
+The Intrinsics employs two levels of locking: application context and
process. Locking an application context ensures mutually exclusive
access by a thread to the state associated with the application context,
including all displays and widgets associated with it. Locking a
-process ensures mutually exclusive access by a thread to (xI process
+process ensures mutually exclusive access by a thread to Intrinsics process
global data.
</para>
+
<para>
-<!-- .LP -->
A client may acquire a lock multiple times and the effect is cumulative.
The client must ensure that the lock is released an equal number of times in
order for the lock to be acquired by another thread.
</para>
+
<para>
-<!-- .LP -->
Most application writers will have little need to use locking as the
-(xI performs the necessary locking internally.
+Intrinsics performs the necessary locking internally.
Resource converters are an exception.
They require the application context or process to be locked
before the application can safely call them directly, for example:
</para>
-<para>
-<!-- .LP -->
-<!-- .KS -->
<literallayout class="monospaced">
-<!-- .TA .5i 2i -->
-<!-- .ta .5i 2i -->
...
XtAppLock(app_context);
XtCvtStringToPixel(dpy, args, num_args, fromVal, toVal, closure_ret);
XtAppUnlock(app_context);
...
</literallayout>
-<!-- .KE -->
-</para>
<para>
-<!-- .LP -->
When the application relies upon
<function>XtConvertAndStore</function>
or a converter to provide the storage for the results of a
conversion, the application should acquire the process lock before
calling out and hold the lock until the results have been copied.
</para>
+
<para>
-<!-- .LP -->
Application writers who write their own
utility functions, such as one which retrieves the being_destroyed field from
a widget instance, must lock the application context before accessing
widget internal data. For example:
</para>
-<para>
-<!-- .LP -->
-<!-- .KS -->
<literallayout class="monospaced">
-<!-- .TA .5i 2i -->
-<!-- .ta .5i 2i -->
#include &lt;X11/CoreP.h&gt;
Boolean BeingDestroyed (widget)
Widget widget;
@@ -5499,16 +4794,11 @@ Boolean BeingDestroyed (widget)
return ret;
}
</literallayout>
-<!-- .KE -->
-A client that wishes to atomically call two or more (xI functions
+<para>
+A client that wishes to atomically call two or more Intrinsics functions
must lock the application context. For example:
</para>
-<para>
-<!-- .LP -->
-<!-- .KS -->
<literallayout class="monospaced">
-<!-- .TA .5i 2i -->
-<!-- .ta .5i 2i -->
...
XtAppLock(XtWidgetToApplicationContext(widget));
XtUnmanageChild (widget1);
@@ -5516,30 +4806,21 @@ must lock the application context. For example:
XtAppUnlock(XtWidgetToApplicationContext(widget));
...
</literallayout>
-<!-- .KE -->
-
-</para>
-<sect4 id="Locking_the_Application_Context">
+<sect3 id="Locking_the_Application_Context">
<title>Locking the Application Context</title>
-<!-- .XS -->
-<!-- <function>(SN Locking the Application Context</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To ensure mutual exclusion of application context, display, or
widget internal state, use
<function>XtAppLock.</function>
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppLock" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAppLock(<emphasis remap='I'>app_context</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppLock'>
+<funcprototype>
+<funcdef>void <function>XtAppLock</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5553,29 +4834,25 @@ Specifies the application context to lock.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtAppLock</function> blocks until it is able to acquire the lock. Locking the
application context also ensures that only the thread holding the lock
makes Xlib calls from within Xt. An application that makes its own
direct Xlib calls must either lock the application context around every
call or enable thread locking in Xlib.
</para>
+
<para>
-<!-- .LP -->
To unlock a locked application context, use
<function>XtAppUnlock.</function>
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppUnlock" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAppUnlock(<emphasis remap='I'>app_context</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppUnlock'>
+<funcprototype>
+<funcdef>void <function>XtAppUnlock</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5588,97 +4865,79 @@ Specifies the application context that was previously locked.
</listitem>
</varlistentry>
</variablelist>
-<para>
-<!-- .LP -->
-<!-- .eM -->
-</para>
-</sect4>
-<sect4 id="Locking_the_Process">
+</sect3>
+<sect3 id="Locking_the_Process">
<title>Locking the Process</title>
-<!-- .XS -->
-<!-- (SN Locking the Process -->
-<!-- .XE -->
<para>
-<!-- .LP -->
To ensure mutual exclusion of (tk process global data, a
widget writer must use
<function>XtProcessLock.</function>
</para>
+
+<funcsynopsis id='XtProcessLock'>
+<funcprototype>
+<funcdef>void <function>XtProcessLock</function></funcdef>
+ <paramdef><parameter></parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<para>
-<!-- .LP -->
-<!-- .IN "XtProcessLock" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtProcessLock()
-<!-- .FN -->
-<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtProcessLock</function> blocks until it is able to acquire the lock.
Widget writers may use XtProcessLock to guarantee mutually exclusive
access to widget static data.
</para>
+
<para>
-<!-- .LP -->
To unlock a locked process, use
-<function>XtProcessUnlock .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtProcessUnlock" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtProcessUnlock</function>.
</para>
-<!-- .FD 0 -->
-void XtProcessUnlock()
-<!-- .FN -->
+
+<funcsynopsis id='XtProcessUnlock'>
+<funcprototype>
+<funcdef>void <function>XtProcessUnlock</function></funcdef>
+ <paramdef><parameter></parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<para>
-<!-- .LP -->
-<!-- .eM -->
To lock both an application context and the process at the same
time, call
<function>XtAppLock</function>
first and then
-<function>XtProcessLock .</function>
+<function>XtProcessLock</function>.
To release both locks, call
<function>XtProcessUnlock</function>
first and then
-<function>XtAppUnlock .</function>
+<function>XtAppUnlock</function>.
The order is important to avoid deadlock.
-
</para>
-</sect4>
</sect3>
-<sect3 id="Event_Management_in_a_Multi_Threaded_Environment">
+</sect2>
+
+<sect2 id="Event_Management_in_a_Multi_Threaded_Environment">
<title>Event Management in a Multi-Threaded Environment</title>
-<!-- .XS -->
-<!-- <function>(SN Event Management in a Multi-Threaded Environment</function> -->
-<!-- .XE -->
<para>
-<!-- .LP -->
In a nonthreaded environment an application writer could reasonably
assume that it is safe to exit the application from a quit callback.
This assumption may no longer hold true in a multi-threaded environment;
therefore it is desirable to provide a mechanism to terminate an
event-processing loop without necessarily terminating its thread.
</para>
+
<para>
-<!-- .LP -->
To indicate that the event loop should terminate after the current
event dispatch has completed, use
-<function>XtAppSetExitFlag .</function>
+<function>XtAppSetExitFlag</function>.
</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppSetExitFlag" "" "@DEF@" -->
-<!-- .sM -->
-</para>
-<!-- .FD 0 -->
-void XtAppSetExitFlag(<emphasis remap='I'>app_context</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppSetExitFlag'>
+<funcprototype>
+<funcdef>void <function>XtAppSetExitFlag</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5692,27 +4951,23 @@ Specifies the application context.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtAppMainLoop</function>
tests the value of the flag and will return if the flag is <function>True</function>.
</para>
+
<para>
-<!-- .LP -->
Application writers who implement their own main loop may test the
value of the exit flag with
-<function>XtAppGetExitFlag .</function>
-</para>
-<para>
-<!-- .LP -->
-<!-- .IN "XtAppGetExitFlag" "" "@DEF@" -->
-<!-- .sM -->
+<function>XtAppGetExitFlag</function>.
</para>
-<!-- .FD 0 -->
-Boolean XtAppGetExitFlag(<emphasis remap='I'>app_context</emphasis>)
-<!-- .br -->
- XtAppContext <emphasis remap='I'>app_context</emphasis>;
-<!-- .FN -->
+
+<funcsynopsis id='XtAppGetExitFlag'>
+<funcprototype>
+<funcdef>Boolean <function>XtAppGetExitFlag</function></funcdef>
+ <paramdef>XtAppContext <parameter>app_context</parameter></paramdef>
+</funcprototype>
+</funcsynopsis>
+
<variablelist>
<varlistentry>
<term>
@@ -5726,8 +4981,6 @@ Specifies the application context.
</varlistentry>
</variablelist>
<para>
-<!-- .LP -->
-<!-- .eM -->
<function>XtAppGetExitFlag</function>
will normally return <function>False</function>, indicating that event processing
may continue. When
@@ -5735,11 +4988,11 @@ may continue. When
returns <function>True</function>, the loop must terminate and return to the caller,
which might then destroy the application context.
</para>
+
<para>
-<!-- .LP -->
Application writers should be aware that, if a thread is blocked in
-<function>XtAppNextEvent ,</function>
-<function>XtAppPeekEvent ,</function>
+<function>XtAppNextEvent</function>,
+<function>XtAppPeekEvent</function>,
or
<function>XtAppProcessEvent</function>
and another thread in the same application context opens a new display,
@@ -5747,124 +5000,17 @@ adds an alternate input, or a timeout, any new source(s) will not
normally be "noticed" by the blocked thread. Any new sources are
"noticed" the next time one of these functions is called.
</para>
+
<para>
-<!-- .LP -->
-The (xI manage access to events on a last-in, first-out basis. If
+The Intrinsics manage access to events on a last-in, first-out basis. If
multiple threads in the same application context block in
-<function>XtAppNextEvent ,</function>
-<function>XtAppPeekEvent ,</function>
+<function>XtAppNextEvent</function>,
+<function>XtAppPeekEvent</function>,
or
-<function>XtAppProcessEvent ,</function>
+<function>XtAppProcessEvent</function>,
the last thread to call one of these functions is the first
thread to return.
-<!-- .bp -->
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
</para>
-</sect3>
</sect2>
+</sect1>
</chapter>
-</book>
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-13 23:16:14 +0000