MirOS Manual: XtRegisterDrawable(3), XtUnregisterDrawable(3)

XtRegisterDrawable(3Xt)   XT FUNCTIONS    XtRegisterDrawable(3Xt)


     XtRegisterDrawable - register a drawable with the Intrisics
     event dispatcher


     void XtRegisterDrawable(Display* display, Drawable drawable,
          Widget widget);

     void XtUnregisterDrawable(Display* display, Drawable draw-


     display   Specifies the drawable's display.

     drawable  Specifies the drawable to register.

     widget    Specifies the widget to register the drawable for.


     XtRegisterDrawable associates the specified drawable with
     the specified widget so that future calls to XtWindowTo-
     Widget with the drawable will return the widget. The default
     event dispatcher will dispatch future core events that
     arrive with the drawable to the widget as though the event
     contained the widget's window, but the event itself will not
     be changed in any way when being passed to even handler or
     action procedures.

     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 XtRegisterDrawable are

     XtUnregisterDrawable removes an association created with
     XtRegisterDrawable. If the drawable is the window of a wid-
     get in the client's widget tree the results of calling
     XtUnregisterDrawable are undefined.


     X Toolkit Intrinsics - C Language Interface
     Xlib - C Language X Interface

XFree86                   Version 4.5.0                         1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.