TICKIT_RECT_INTERSECTS(3)

💖 TICKIT_RECT_INTERSECTS 💖

okay bestie, welcome to the tickit_rect_intersects(3) page, straight out of the Library Functions Manual 🫶 this one lives in section 3 with all the other library functions, and it's genuinely so simple it's giving main character energy for like three lines of code. no cap.

✨ NAME ✨

tickit_rect_intersects — test if two rectangles intersect 🦋

🌸 SYNOPSIS 🌸

#include <tickit.h>

bool tickit_rect_intersects(const TickitRect *a, const TickitRect *b);

Link with -ltickit. 💅 (yes you literally have to link it, don't forget, i'm begging)

💫 DESCRIPTION 💫

so tickit_rect_intersects() does exactly one (1) thing and it eats: it tests whether the two given rectangles intersect at all 🔥

it returns true if there is a non-empty rectangular region in common that's covered by both rectangles. that's the whole vibe check. if they overlap even a little, true. if they're just touching edges or fully apart, no overlap, no true, periodt.

and listen — if you want the actual intersection region itself, not just the yes/no answer, tickit_rect_intersect(3) can be used to obtain this intersection as well as performing the intersection test itself 👑 like, it does both. iconic of it honestly.

🎀 RETURN VALUE 🎀

tickit_rect_contains() returns a boolean value.

okay bestie i know, the name in that sentence looks sus — i'm just telling you what the page says, word for word, no edits from me 🙈 it returns a boolean value, that's the tea. 🍓

🌈 SEE ALSO 🌈

• tickit_rect_init_sized(3)
• tickit_rect_init_bounded(3)
• tickit_rect_contains(3)
• tickit_rect_intersect(3)
• tickit_rect(7)
• tickit(7)

and that's the whole page bestie, we ate 💅✨ this came to you from the Library Functions Manual, TICKIT_RECT_INTERSECTS(3), section 3, no date listed on this one so i can't give you a timestamp, just pure library-functions-manual energy 🧚💜 go forth and check your rectangle overlaps, ily, bye 🫶