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 a GraphicsExpose event to a client application, it sends an XGraphicsExposeEvent structure with the type member set to GraphicsExpose.
  • display β€” set to a pointer to the display the event was read on. like, β€œwhere was this event read from?” energy.
  • send_event β€” set to True if the event came from a SendEvent protocol 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, window shows up twice on this page β€” it’s giving double duty.
  • value_mask β€” indicates which components were specified in the ConfigureWindow protocol 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 of above (sibling) and detail (stack-mode), which are reported as None and Above, respectively, if they are not given in the request. 🫢

🌈 SEE ALSO 🌈

the whole Xlib event squad, in the exact order:

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