XAllowEvents(3)

📦
version 1.8.14 · 8 versions
, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable

okay bestie, welcome to the XAllowEvents(3) page — part of the Xlib functions family, and she is lowkey iconic 💅✨

🌸 NAME 🌸

XAllowEvents — release queued events 🎀

✨ SYNTAX ✨

int XAllowEvents(Display *display, int event_mode, Time time);

🎀 ARGUMENTS 🎀

  • display — Specifies the connection to the X server. like, which X server connection we're talking to, bestie 💖
  • event_mode — Specifies the event mode. You can pass AsyncPointer, SyncPointer, AsyncKeyboard, SyncKeyboard, ReplayPointer, ReplayKeyboard, AsyncBoth, or SyncBoth. pick your fighter, no cap 👑
  • time — Specifies the time. You can pass either a timestamp or CurrentTime. timestamp or CurrentTime, those are the options 🕰️

🦋 DESCRIPTION 🦋

The XAllowEvents function releases some queued events if the client has caused a device to freeze. it's giving “let the queued events out,” but only in that specific situation ✨

It has no effect if the specified time is earlier than the last-grab time of the most recent active grab for the client or if the specified time is later than the current X server time. so yeah, the time check is doing main character energy — outside that window, she's not doing anything 💅

XAllowEvents can generate a BadValue error. heads up, bestie 🚨

💀 DIAGNOSTICS 💀

  • BadValue — Some numeric value falls outside the range of values accepted by the request. Unless a specific range is specified for an argument, the full range defined by the argument's type is accepted. Any argument defined as a set of alternatives can generate this error. so if a number is giving “not in my range,” this is the error that shows up 🙈

🌈 SEE ALSO 🌈

  • Xlib - C Language X Interface the classic, iykyk 🫶

💖 and that's the tea. this page is signing off with X Version 11 and libX11 1.8.14 — XAllowEvents(3) footer energy, periodt. 🎀🦋

📦 where this page comes from