al_get_separate_bitmap_blender(3alleg5)

📦
version 5.2.11.3 · 4 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 al_get_separate_bitmap_blender — Allegro 5 API 💖

ok so bestie, you're in the 3alleg5 manual, and today's main character is al_get_separate_bitmap_blender. it's giving "let me peek at your blender settings" and honestly? iconic. 🎀

✨ 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 🌸

okay so picture this: the target bitmap has a blender, right? and it's currently living its life, blending away. this function is basically the vibe check — it hands you back the current blender that the target bitmap is using. 🫶

six pointers, six little output slots, and the vibes are:

  • op — the color operation
  • src — the color source
  • dst — the color destination
  • alpha_op — the alpha operation
  • alpha_src — the alpha source
  • alpha_dst — the alpha destination

and here's the part that lowkey saves your life: you can pass NULL for any values you are not interested in. don't care about alpha? NULL it. only here for op? NULL, NULL, NULL, NULL, NULL, and slay. 💅 the function will not be weird about it.

⭐ SINCE ⭐

5.2.5

[Unstable API]: New API. 💀 yes girl, it's marked unstable — act accordingly, no cap.

🦋 SEE ALSO 🦋

and that's the whole page, bestie 💜 this was the Allegro reference manual serving you al_get_separate_bitmap_blender(3alleg5) — go forth, check those blenders, and remember: NULL is not a red flag here, it's a personality trait. ✨🎀

📦 where this page comes from