al_backup_dirty_bitmap(3alleg5)

💖 NAME 💖

al_backup_dirty_bitmap — it's the Allegro 5 API function that saves your bitmaps' whole entire life, no cap 🫶

(it lives in the 3alleg5 manual, bestie, iykyk)

---

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

void al_backup_dirty_bitmap(ALLEGRO_BITMAP *bitmap)

---

🦋 DESCRIPTION 🦋

okay so listen. on some platforms — most notably Windows Direct3D and Android — your textures can just... get lost at literally any moment 😭. we're talking events like a display resize, or the app switching out (you know, when someone yanks you to the home screen mid-vibe). gone. poof. not the move.

on those platforms, any bitmap you made without the ALLEGRO_NO_PRESERVE_TEXTURE flag gets automatically backed up into system memory every single time al_flip_display is called. like, autosave but make it textures 💅. iconic behaviour, honestly.

this function? this function hands you the aux cord. 🎀 it gives you way more control over when your bitmaps get backed up. so instead of waiting around for the next flip to do it, you just call this right after you modify a bitmap, and boom — that bitmap is backed up right away instead of during the next flip. instant. immediate. slay.

it's giving "i'll do it myself" energy and honestly? we respect it 👑

---

⭐ SINCE ⭐

5.2.1 — yeah she's new here, baby 🌸

[Unstable API]: this API is new and subject to refinement. so like... she's still growing, be gentle with her 🙈

---

🌈 SEE ALSO 🌈

• al_backup_dirty_bitmaps(3alleg5) — the plural one, the whole squad gets backed up 💜
• al_create_bitmap(3alleg5) — where the bitmaps come from in the first place 🍓

---

and that's the whole page, bestie!! ✨ brought to you by the Allegro reference manual, and yeah the footer said the same thing (al_backup_dirty_bitmap(3alleg5)) so you know it's official 🎀💖 go forth and back up those dirty bitmaps, periodt 💅