TICKIT_WATCH_LATER(3)

💖 TICKIT_WATCH_LATER 💖

okay bestie, welcome to tickit_watch_later(3) — it's a Library Functions Manual page, it's giving "schedule a callback for the very next round of IO events", and honestly? it ate. let's get into it 🫶

---

✨ NAME ✨

tickit_watch_later — invoke a callback at the next round of IO events

like, the next one. not now. next. periodt. 💅

---

🌸 SYNOPSIS 🌸

#include <tickit.h>

typedef int TickitCallbackFn(Tickit *t, TickitEventflags flags,
    void *info, void *user);

void *tickit_watch_later(Tickit *t, TickitBindFlags flags,
    TickitCallbackFn *fn, void *user);

and you gotta link it, no cap:

Link with -ltickit.

---

🦋 DESCRIPTION 🦋

so tickit_watch_later() registers a callback function that the toplevel event loop is gonna invoke as it processes the next round of IO events. a registered callback gets invoked by a running call to tickit_run(3). and here's the iconic part: the callback function gets invoked once, and then it's destroyed afterwards. one and done, main character energy, no encore. 💀

the info pointer will be NULL. just so you know. it's not ghosting you, it's literally NULL. 🙈

when it does get invoked, the callback function is always passed both TICKIT_EV_FIRE and TICKIT_EV_UNBIND flags to its flags argument. both. always. that's the vibe check and it passed. ✅

and if the callback had been registered with the TICKIT_BIND_DESTROY flag, then it will also be invoked with the TICKIT_EV_DESTROY flag if it has not yet been invoked by the time the toplevel instance is destroyed. so like, if the toplevel dips before your callback got its moment, it still shows up — just with TICKIT_EV_DESTROY instead. lowkey sweet of it fr fr 🥹

now, queue placement, because order matters bestie:

• if you registered with the TICKIT_BIND_FIRST flag, the callback will be inserted at the start of the queue, coming before others. cutting the line, but make it legal. 👑
• if not, it is appended at the end. respectfully waiting its turn. 🌈

and one more thing — if it gets cancelled by tickit_watch_cancel(3), the callback function is invoked with just the TICKIT_EV_UNBIND flag, but only if it had been registered with TICKIT_BIND_UNBIND. just the one flag. not both. read that twice, i know i did 😭

---

⭐ RETURN VALUE ⭐

tickit_watch_later() returns an opaque identifier pointer. that's it, that's the whole return value. hold onto it like it's a concert ticket bestie 🎀

---

💜 SEE ALSO 💜

the whole friend group, obviously:

• tickit_new_stdio(3)
• tickit_watch_io(3)
• tickit_watch_timer_after_msec(3)
• tickit_watch_timer_at_epoch(3)
• tickit_watch_signal(3)
• tickit_watch_process(3)
• tickit_watch_cancel(3)
• tickit(7)

---

and that's the page!! this was TICKIT_WATCH_LATER(3), living in the Library Functions Manual, and yes the title really is just its own name again because manpages are extra like that 💅 go schedule something for the next round of IO events, you deserve it ✨💖