XtAppNextEvent, XtAppPending, XtAppPeekEvent, XtAppProcessEvent, XtDispatchEvent, XtAppMainLoop − query and process events and input


void XtAppNextEvent(XtAppContext app_context, XEvent *event_return);

Boolean XtAppPeekEvent(XtAppContext app_context, XEvent *event_return);

XtInputMask XtAppPending(XtAppContext app_context);

void XtAppProcessEvent(XtAppContext app_context, XtInputMask mask);

Boolean XtDispatchEvent(XEvent *event);

void XtAppMainLoop(XtAppContext app_context);



Specifies the application context that identifies the application .


Specifies a pointer to the event structure that is to be dispatched to the appropriate event handler.


Returns the event information to the specified event structure.


Specifies what types of events to process. The mask is the bitwise inclusive OR of any combination of XtIMXEvent, XtIMTimer, XtIMAlternateInput, and XtIMSignal. As a convenience, the X Toolkit defines the symbolic name XtIMAll to be the bitwise inclusive OR of all event types.


If the X event queue is empty, XtAppNextEvent flushes the X output buffers of each Display in the application context and waits for an event while looking at the other input sources, timeout timeout values, and signal handlers and calling any callback procedures triggered by them. This wait time can be used for background processing (see Section 7.8).

If there is an event in the queue, XtAppPeekEvent fills in the event and returns a nonzero value. If no X input is on the queue, XtAppPeekEvent flushes the output buffer and blocks until input is available (possibly calling some timeout callbacks in the process). If the input is an event, XtAppPeekEvent fills in the event and returns a nonzero value. Otherwise, the input is for an alternate input source, and XtAppPeekEvent returns zero.

The XtAppPending function returns a nonzero value if there are events pending from the X server, timer pending, or other input sources pending. The value returned is a bit mask that is the OR of XtIMXEvent, XtIMTimer, XtIMAlternateInput, and XtIMSignal (see XtAppProcessEvent). If there are no events pending, XtAppPending flushes the output buffer and returns zero.

The XtAppProcessEvent function processes one timer, alternate input, signal source, or X event. If there is nothing of the appropriate type to process, XtAppProcessEvent blocks until there is. If there is more than one type of thing available to process, it is undefined which will get processed. Usually, this procedure is not called by client applications (see XtAppMainLoop). XtAppProcessEvent processes timer events by calling any appropriate timer callbacks, alternate input by calling any appropriate alternate input callbacks, signal source by calling any appropriate signal callbacks, and X events by calling XtDispatchEvent.

When an X event is received, it is passed to XtDispatchEvent, which calls the appropriate event handlers and passes them the widget, the event, and client-specific data registered with each procedure. If there are no handlers for that event registered, the event is ignored and the dispatcher simply returns. The order in which the handlers are called is undefined.

The XtDispatchEvent function sends those events to the event handler functions that have been previously registered with the dispatch routine. XtDispatchEvent returns True if it dispatched the event to some handler and False if it found no handler to dispatch the event to. The most common use of XtDispatchEvent is to dispatch events acquired with the XtAppNextEvent procedure. However, it also can be used to dispatch user-constructed events. XtDispatchEvent also is responsible for implementing the grab semantics for XtAddGrab.

The XtAppMainLoop function first reads the next incoming X event by calling XtAppNextEvent and then it dispatches the event to the appropriate registered procedure by calling XtDispatchEvent. This constitutes the main loop of X Toolkit applications, and, as such, it does not return unless XtAppSetExitFlag is called. Applications are expected to exit in response to some user action. There is nothing special about XtAppMainLoop; it is simply an loop that calls XtAppNextEvent and then XtDispatchEvent, until XtAppGetExitFlag() returns true.

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 XtAppNextEvent.


X Toolkit Intrinsics − C Language Interface
Xlib − C Language X Interface

More Linux Commands

XtChangeManagedSet(3) - manage and unmanage children........
The XtManageChildren function performs the following: * Issues an error if the children do not all have the same parent or if the parent is not a subclass of co

imon.8 (Manual - Linux man page)...........................
imon is a ncurses based utility for watching ISDN activity. OPTIONS -q If this option is given, the facility of terminatig the program by pressing Q is disabled

SDL_CDtrack(3) - CD Track Information Structure (Man Page)
SDL_CDtrack stores data on each track on a CD, its fields should be pretty self explainatory. It is a member a the SDL_CD structure. Note: Frames can be convert

glEvalMesh(3gl) - compute a one- or two-dimensional grid of
glMapGrid and glEvalMesh are used in tandem to efficiently generate and evaluate a series of evenly-spaced map domain values. glEvalMesh steps through the integ

perlutil(1) - utilities packaged with the Perl distribution
Along with the Perl interpreter itself, the Perl distribution installs a range of utilities on your system. There are also several utilities which are used by t

XIGrabEnter(3) - grab/ungrab enter or focus in events.......
XIGrabEnter and XIGrabFocusIn establish a passive grab. The modifier device for a enter grab is the paired master device if deviceid specifies a master pointer.

acecad(4) - Acecad Flair input driver - Linux manual page...
acecad is an Xorg input driver for Acecad Flair devices... The acecad driver functions as a pointer input device, and may be used as the X servers core pointer.

Tcl_RestoreResult(3) - save and restore an interpreter's sta
These routines allows a C procedure to take a snapshot of the current │ state of an interpreter so that it can be restored after a call to │ Tcl_Eva

nmbd(8) - NetBIOS name server to provide NetBIOS over IP nam
This program is part of the samba(7) suite. nmbd is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB

lnstat(8) - unified linux network statistics (Man Page).....
This manual page documents briefly the lnstat command. lnstat is a generalized and more feature-complete replacement for the old rtstat program. In addition to

XML::DOM::CharacterData(3pm) - Common interface for Text, CD
XML::DOM::CharacterData extends XML::DOM::Node The CharacterData interface extends Node with a set of attributes and methods for accessing character data in the

string(n) - Manipulate strings (Local - Linux man page).....
Performs one of several string operations, depending on option. The legal options (which may be abbreviated) are: string cat ?string1? ?string2...? Concatenate

We can't live, work or learn in freedom unless the software we use is free.