al_is_bitmap_locked(3alleg5)
π al_is_bitmap_locked β the Allegro 5 API
okay so bestie, welcome to the al_is_bitmap_locked page of the allegro5 manual (section 3, the library-calls girlies π). it's short, it's sweet, it's giving "one job and she does it" energy. let's go β¨
β¨ NAME β¨
al_is_bitmap_locked β Allegro 5 API π¦
πΈ SYNOPSIS πΈ
#include <allegro5/allegro.h>
bool al_is_bitmap_locked(ALLEGRO_BITMAP *bitmap)
like yes, that's the whole thing. include the header, call the function, get a bool back. iconic behavior fr fr π
π DESCRIPTION π
so what does she do?? she tells you whether or not a bitmap is already locked. that's it. that's the vibe check π
you hand her an ALLEGRO_BITMAP *bitmap, she hands you back the truth β is it locked, or is it not. no cap, no drama, no side quests. just answers π«Ά
ngl the "already" is doing a lot of work there β she's checking the current state of that bitmap, not locking anything for you. if you were hoping she'd lock it, she will not. that's a different girl (see below π).
π SEE ALSO π
go read those too, they're the ones actually doing the locking and unlocking. this page is just the check-in text, the "u up?" of the bitmap world π
and that's the whole page, bestie!! this was the Allegro reference manual's take on al_is_bitmap_locked(3alleg5), served up fresh from section 3. mwah π stay locked (or don't, honestly, please unlock your bitmaps) πβπ
π¦ where this page comes from
- debian trixie: allegro5-doc 2:5.2.10.1+dfsg-1 Β· Zlib
- ubuntu questing: allegro5-doc 2:5.2.10.1+dfsg-1build1
- ubuntu resolute: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- ubuntu stonking: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms