al_get_event_source_data(3alleg5)
okay so bestie, welcome to the al_get_event_source_data(3alleg5) page β it's giving Allegro 5 API energy and honestly? It's a short one, so let's get into it π
π¦ NAME π¦
al_get_event_source_data β the Allegro 5 API function that lowkey just gets the data you stashed on an event source. No cap.
β¨ SYNOPSIS β¨
#include <allegro5/allegro.h>
intptr_t al_get_event_source_data(const ALLEGRO_EVENT_SOURCE *source)
πΈ DESCRIPTION πΈ
So like, this function returns the abstract user data that's associated with the event source. You know, the lil custom pointer or whatever you attached earlier? It hands it back to you.
If no data was previously set, it returns NULL. That's it. That's the whole vibe. No drama, no surprises.
fr fr, if you get NULL back, it just means nobody set anything yet β not a bug, just a blank slate π«Ά
π SEE ALSO π
al_set_event_source_data(3alleg5)β the setter to this getter, the other half of the iconic duo β¨
k bye bestie, this page came straight from the Allegro reference manual β no date listed but it's timeless anyway. Stay slaying those event sources ππ
π¦ 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