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

XtPeekEvent()							 XtPeekEvent()

Name
  XtPeekEvent  -  return,  but do not remove the event at  the head of an
  application's input queue.

Synopsis
  Boolean XtPeekEvent(event_return)
	 XEvent *event_return;

Inputs
  event_return
	      Returns the event information from the head event structure
	      in the queue.

Returns
  True	if  the event at the head of the queue is an X event; False if it
  is a timer event or an alternate input source event.

Availability
  XtPeekEvent() has been superseded by XtAppPeekEvent().

Description
  XtPeekEvent() returns a copy of the X event at the head  of  the  input
  queue,  without removing it from the queue.  If there is an X event, it
  returns True.	 If there are no X events pending, but there are timer or
  alternate  events, XtPeekEvent() returns False.  If there are no events
  pending, XtPeekEvent() blocks.

Usage
  XtPeekEvent() has been superseded by XtAppPeekEvent(),  which	 performs
  the  same  function  on a per-application context basis.  XtPeekEvent()
  now calls XtAppPeekEvent() passing the default application context cre‐
  ated	by  XtInitialize().   Very few programs need multiple application
  contexts, and you can continue to use XtPeekEvent() if  you  initialize
  your	application with XtInitialize().  We recommend, however, that you
  use XtAppInitialize(), XtAppPeekEvent(), and the other XtApp*()  appli‐
  cation context specific functions.

  See XtAppPeekEvent() 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).

Xt - Event Handling						 XtPeekEvent()

Vote for polarhome