Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   10987 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

XtProcessEvent()					      XtProcessEvent()

Name
  XtProcessEvent - get and process one input event of a specified type.

Synopsis
  void XtProcessEvent(mask)
	 XtInputMask mask;

Inputs
  mask	    Specifies what types of events to process.

Availability
  XtProcessEvent() has been superseded by XtAppProcessEvent().

Description
  XtProcessEvent() processes one X event, alternate input source event or
  timer event.	The mask argument specifies which types of events are  to
  be  processed;  it is the bitwise inclusive OR ( ) of any of the values
  XtIMXEvent, XtIMTimer, or  XtIMAlternateInput,  or  the  value  XtIMAll
  which specifies all three event types.  XtProcessEvent() calls any reg‐
  istered background work procedures if there are  no  events  available,
  and blocks if there are no events and no work procedures.

Usage
  XtProcessEvent() has been superseded by XtAppProcessEvent(), which per‐
  forms the same function on a per-application context basis.	XtProces‐
  sEvent()			      now			    calls
  XtAppProcessEvent() passing the default application context created  by
  XtInitialize().   Very few programs need multiple application contexts,
  and				    you				      can
  continue  to	use  XtProcessEvent()  if you initialize your application
  with
  XtInitialize().  We recommend, however, that you use XtAppInitialize(),
  XtAppProcessEvent(), and the other XtApp*()  application  context  spe‐
  cific functions.

  See XtAppProcessEvent() for more information.

  Programs rarely need this much control over the event dispatching mech‐
  anism.  Most programs use XtAppMainLoop().

See Also
  XtAppMainLoop(1), XtAppPeekEvent(1), XtAppPending(1), XtAppProcessEv‐
  ent(1).

Xt - Event Handling					      XtProcessEvent()

Vote for polarhome