create_sub_bitmap(3alleg4)

✨ NAME ✨

create_sub_bitmap — bestie, it literally creates a memory sub bitmap 💅. Part of the Allegro game programming library, no cap. 🎀

🦋 SYNOPSIS 🦋

#include <allegro.h>

BITMAP *create_sub_bitmap(BITMAP *parent, int x, y, width, height);

🌸 DESCRIPTION 🌸

Okay so picture this: you've got a bitmap already, right? A whole entire parent bitmap, living its main character life. Now create_sub_bitmap makes you a sub-bitmap — which is a bitmap that shares its drawing memory with that pre-existing bitmap, but it can have its own different size and its own clipping settings. It's giving "we're not copies, we're connected." 🫶

Tiny but crucial detail: when you're making a sub-bitmap of the mode-X screen, the x position must be a multiple of four. Like, that's not a suggestion, that's the vibe check. 🔥

The sub-bitmap's width and height can totally extend past the right and bottom edges of the parent — they'll just get clipped, nbd 🙈. But the origin point has to lie inside the parent region. That part is non-negotiable, bestie. 👑

💖 RETURN VALUE 💖

It hands you back a pointer to the freshly created sub bitmap, all sparkly and new ✨. Or, if the sub bitmap couldn't be created, you get NULL — and honestly? Not iconic, but it happens. 😭

⚠️ GIRL, LISTEN ⚠️ Remember to free the sub bitmap before you free the parent bitmap! Otherwise you get memory leaks and potentially crashes from accessing memory that's already been freed. That's not a fun surprise, that's a jumpscare. 💀

⭐ SEE ALSO ⭐

• create_bitmap(3alleg4)
• create_bitmap_ex(3alleg4)
• destroy_bitmap(3alleg4)
• is_sub_bitmap(3alleg4)
• clear_bitmap(3alleg4)
• clear_to_color(3alleg4)
• expat(3alleg4)
• exscroll(3alleg4)
• exswitch(3alleg4)

Okay that's the whole page, you ate that 🍓 — this was Allegro, version 4.4.3, and yes, the page is literally named create_sub_bitmap(3alleg4). Go forth and make sub-bitmaps, queen. 💜🧚