XpEndPage(3Xp)

💅 XpEndPage(3Xp) — literally the "we're done with this page" era

okay bestie, welcome to the XPRINT FUNCTIONS section of the manual, and today's main character is XpEndPage ✨ this one is short and sweet, no cap.

---

🌸 NAME 🌸

XpEndPage — signals that a print page is over, like when you finally hit "done" on a photo dump 📸

---

🦋 SYNOPSIS 🦋

      cc [ flag... ] file... -lXp [ library... ]
      #include <X11/extensions/Print.h>

void XpEndPage ( display )
      Display *display;

---

💖 DESCRIPTION 💖

okay so XpEndPage signals the end of a print page, and it causes window to be unmapped. that's the whole vibe. 🫶

all the resulting page data gets assembled and combined with data you previously sent over with XpPutDocumentData. and listen — after XpEndPage is called, there will be no generation of document data for rendering operations to the corresponding windows. like, that window is clocked out, periodt. 💀

and for clients selecting XPPrintMask (peep XpSelectInput for that), the event XPPrintNotify is generated with its detail field set to XPEndPageNotify — and that happens when the X Print Server has completed XpEndPage. so you get the lil confirmation notification, iconic behavior honestly 👑

---

🎀 ARGUMENTS 🎀

• display — specifies a pointer to the Display structure; this is the one you got back from XOpenDisplay. don't lose it bestie 🙈

---

🔥 DIAGNOSTICS 🔥

• XPBadSequence — the function was not called in the proper order with respect to the other X Print Service Extension calls. example of the mess: XpStartPage was called before XpStartJob, or was called for a type XPDocRaw document. sequence matters, queen, this is not a free-for-all 😭

---

🌈 SEE ALSO 🌈

• XpPutDocumentData.(3Xp)
• XpSelectInput(3Xp)
• XpStartPage(3Xp)

---

ngl the vibes here are "you started the page, now finish it" — order matters or the X Print Server will absolutely call you out with XPBadSequence 💅

that's the whole page, go be great 🦋

X Version 11, libXp 1.0.4 — mwah, that's a wrap, xoxo 🎀💜