al_backup_dirty_bitmap(3)

💾 al_backup_dirty_bitmap(3) — the Allegro 5 API glow-up ✨

Okay bestie, so this one's from the Library Functions Manual and it's literally the Allegro 5 API. Let's get into it 🫶

---

🌸 NAME 🌸

al_backup_dirty_bitmap — Allegro 5 API, the "save my texture before it gets yeeted" function 💅

---

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

void al_backup_dirty_bitmap(ALLEGRO_BITMAP *bitmap)

---

🦋 DESCRIPTION 🦋

So here's the tea ☕: on some platforms — notably Windows Direct3D and Android — textures can be lost at any time 😭 for events like display resize or switching out of the app. Like, they're just gone, no cap.

On those platforms, bitmaps created without the ALLEGRO_NO_PRESERVE_TEXTURE flag automatically get backed up to system memory every single time al_flip_display is called. Iconic behaviour, honestly 👑

This function gives you more control over when your bitmaps get backed up 💖. By calling this function after modifying a bitmap, you can make sure the bitmap is backed up right away instead of during the next flip. It's giving "I'll do it myself" energy, and we love that for you.

---

🎀 SINCE 🎀

5.2.1 — a whole era 💫

⚠️ [Unstable API]: This API is new and subject to refinement. So like, it works, but it might change on you — proceed with your eyes open, bestie 🙈

---

🔥 SEE ALSO 🔥

• al_backup_dirty_bitmaps(3) — the plural version, for when you have main character energy and multiple bitmaps 👯
• al_create_bitmap(3) — where the bitmap came from in the first place 💜

---

And that's the whole page, periodt 🌈. This slay of a manual page comes courtesy of the Allegro reference manual, dated with all the love from the fine folks who write these things — go forth and back up your textures, bestie 🧚🍓💖