xpaxt(n)

📦 version 2.1.20, in fedora 43, fedora 44

💖 NAME 💖

XPAXt — the XPA Interface to Xt (X Windows) 🪟✨

🌸 SYNOPSIS 🌸

Okay so bestie, this page describes how XPA access points can be added to X Toolkit (Xt) programs. That's the whole vibe. 💅

🦋 DESCRIPTION 🦋

XPA is literally so supportive of Xt programs, no cap: you can call XPANew(), XPACmdNew(), or XPAInfoNew() inside any C routine to add XPA server callbacks to an Xt program. 🫶

But here's the thing, bestie — an Xt program already has its own event loop call (i.e., XtAppMainLoop()), so it does not need or want to use the XPA event loop. Not even a little. She's booked and busy. 🙅‍♀️

So, in order to add XPA access points to the standard Xt event loop, you should call the following routine before entering the loop:

int XPAXtAddInput(XtAppContext app, XPA xpa)

The XPAAddAddInput() routine will add XPA access points to the Xt event loop by making calls to the standard XtAppAddInput() routine. ✨

  • If the XtAppContext argument is NULL, then the alternate XtAddInput() routine is used instead. 🌀
  • If the xpa argument is NULL, then all active XPA access points are added to the loop. 👑
  • If xpa is not NULL, then only the specified access point is added. 🎯

That last type of call is the one you use to add new access points from within a callback, after the program has already entered the XtAppMainLoop() even loop. Like, mid-party, new guest arrives, and you're just letting them in. 🚪💃

ngl, if you're writing Xt code, this is the move. Set it up before the loop and you're golden. 🏆

🔥 SEE ALSO 🔥

See xpa(n) for a list of XPA help pages 📚💖

version 2.1.15 · July 23, 2013 · SAORD Documentation

That's the whole page, bestie — version 2.1.15, dated July 23, 2013, straight from SAORD Documentation. Read it, love it, ship it. 💅✨🦋🎀

📦 where this page comes from