XConfigureRequestEvent(3)
π NAME π
okay bestie, you've landed on XConfigureRequestEvent(3) β a page from XLIB FUNCTIONS β and it's literally the ConfigureRequest event structure. That's the NAME section, no cap. π¦
β¨ STRUCTURES β¨
The structure for ConfigureRequest events contains this, and we are not skipping a single field:
typedef struct {
int type; /* ConfigureRequest */
unsigned long serial; /* # of last request processed by server */
Bool send_event; /* true if this came from a SendEvent request */
Display *display; /* Display the event was read from */
Window parent;
Window window;
int x, y;
int width, height;
int border_width;
Window above;
int detail; /* Above, Below, TopIf, BottomIf, Opposite */
unsigned long value_mask;
} XConfigureRequestEvent;
When you receive this event, the structure members are set as follows. Field-by-field lore time:
typeβ set to the event type constant name that uniquely identifies it. Example: when the X server reports aGraphicsExposeevent to a client application, it sends anXGraphicsExposeEventstructure with thetypemember set toGraphicsExpose.displayβ set to a pointer to the display the event was read on. like, βwhere was this event read from?β energy.send_eventβ set toTrueif the event came from aSendEventprotocol request.serialβ set from the serial number reported in the protocol, but expanded from the 16-bit least-significant bits to a full 32-bit value. tiny bits, full 32-bit glow-up.windowβ set to the window that is most useful to toolkit dispatchers.
Then the rest of the reconfigure info:
parentβ set to the parent window.windowβ set to the window whose size, position, border width, and/or stacking order is to be reconfigured. yes,windowshows up twice on this page β itβs giving double duty.value_maskβ indicates which components were specified in theConfigureWindowprotocol request. The corresponding values are reported as given in the request. The remaining values are filled in from the current geometry of the window, except in the case ofabove(sibling) anddetail(stack-mode), which are reported asNoneandAbove, respectively, if they are not given in the request. π«Ά
π SEE ALSO π
the whole Xlib event squad, in the exact order:
XAnyEvent(3)XButtonEvent(3)XCreateWindowEvent(3)XCirculateEvent(3)XCirculateRequestEvent(3)XColormapEvent(3)XConfigureEvent(3)XCrossingEvent(3)XDestroyWindowEvent(3)XErrorEvent(3)XExposeEvent(3)XFocusChangeEvent(3)XGraphicsExposeEvent(3)XGravityEvent(3)XKeymapEvent(3)XMapEvent(3)XMapRequestEvent(3)XPropertyEvent(3)XReparentEvent(3)XResizeRequestEvent(3)XSelectionClearEvent(3)XSelectionEvent(3)XSelectionRequestEvent(3)XUnmapEvent(3)XVisibilityEvent(3)
And the big-picture one: Xlib - C Language X Interface. π
that's the page, bestie! the original footer stamps this as X Version 11, libX11 1.8.14, and XConfigureRequestEvent(3) β source/version/date-line energy, fr fr. ππ
β¨
π¦ where this page comes from
- alpine 3.24: libx11-doc 1.8.14-r0 Β· X11
- arch rolling: libx11 1.8.14-1 Β· MIT AND X11
- nixos 26.05: libx11 1.8.14
- nixpkgs unstable: libx11 1.8.14
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms