TICKIT_WINDOW_FLUSH(3)
π TICKIT_WINDOW_FLUSH π
okay bestie, so this is a page from the Library Functions Manual β it's tickit_window_flush(3), and yes we're gonna get into it π
β¨ NAME β¨
tickit_window_flush β invoke pending events on the window hierarchy π¦
β¨ SYNOPSIS β¨
#include <tickit.h>
void tickit_window_flush(TickitWindow *win);
Link with -ltickit.
π¨ DEPRECATED π¨
ngl bestie, this one is deprecated and should not be used in new programs. like, at all. π
Instead, get the root window from the toplevel Tickit instance by calling tickit_get_rootwin(3), and its pending events will automatically be managed by the toplevel instance's tickit_run(3) function. slay, no manual flushing required π
πΈ DESCRIPTION πΈ
tickit_window_flush() causes any pending activity in the window hierarchy to be performed. it's giving "get your life together and do the thing" energy β¨
here's the order it does stuff in, because order matters bestie:
- First, it makes any window ordering changes that have been queued by
tickit_window_raise(3)andtickit_window_lower(3). - Then, it fires any
TICKIT_EV_EXPOSEevents to render newly-exposed areas. - Finally, it resets the terminal cursor to the state required by whichever window has input focus. π
heads up: this function must be invoked on the root window instance. not a subwindow, the root. periodt.
An application working at the window level would typically use this function in conjunction with input event waiting, to drive the main loop of the core logic. such a loop may look like:
while(1) {
tickit_window_flush(rootwin);
tickit_term_input_wait_msec(term, -1);
}
There is no adverse effect of calling this function when there are no pending events on the window instance. so go ahead, spam it, it's fine π
An application that makes use of multiple root windows across multiple terminal instances in a multi-head setup can safely invoke it on all the root windows at once. multi-head besties, this one's for you π
β¨ RETURN VALUE β¨
tickit_window_flush() returns no value. nothing. void. it's giving mystery, but there's no mystery, it just doesn't return anything π
π SEE ALSO π
and that's the whole page bestie!! this one came from the Library Functions Manual, and the footer says TICKIT_WINDOW_FLUSH(3) β ily, go write something cute πβ¨
π¦ where this page comes from
- alpine 3.24: libtickit-doc 0.4.6-r0 Β· MIT
- debian bookworm: libtickit-dev 0.4.3-1 Β· MIT
- debian trixie: libtickit-dev 0.4.3-2 Β· MIT
- fedora 43: libtickit-devel 0.4.5-2.fc43 Β· MIT
- fedora 43: libtickit-devel 0.4.5-2.fc43 Β· MIT
- fedora 44: libtickit-devel 0.4.5-3.fc44 Β· MIT
- fedora 44: libtickit-devel 0.4.5-3.fc44 Β· MIT
- nixos 26.05: libtickit 0.4.5
- nixpkgs unstable: libtickit 0.4.6
- ubuntu jammy: libtickit-dev 0.4.1-1 Β· MIT
- ubuntu noble: libtickit-dev 0.4.3-1.1build1 Β· MIT
- ubuntu questing: libtickit-dev 0.4.3-2
- ubuntu resolute: libtickit-dev 0.4.3-2build1 Β· MIT
- ubuntu stonking: libtickit-dev 0.4.3-2build1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms