al_get_sep...ap_blender(3)

πŸ“¦
version 5.2.11.3 Β· 3 versions
, in arch rolling

al_get_sep...ap_blender(3) β€” okay so this is from the Library Functions Manual, and it’s giving Allegro 5 API realness, bestie.

πŸŽ€ NAME πŸŽ€

al_get_separate_bitmap_blender β€” Allegro 5 API</p>, no cap.

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

void al_get_separate_bitmap_blender(int *op, int *src, int *dst, int *alpha_op, int *alpha_src, int *alpha_dst)

πŸ’… DESCRIPTION πŸ’…

Returns the current blender being used by the target bitmap. That’s the whole vibe.

You can pass NULL for values you are not interested in β€” iconic, honestly. Lowkey convenient, highkey useful.

⭐ SINCE ⭐

5.2.5

[Unstable API]: New API. So yeah, it’s new-new and marked unstable β€” main character energy with a tiny caution sticker πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹


Footer check, because we stay informed: this one comes from the Allegro reference manual, it tags the page as al_get_sep...ap_blender(3), and the date slot is literally not filled in on this page β€” so no fake date from me, fr fr πŸ’–

πŸ“¦ where this page comes from
  • arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms