al_get_touch_...n_event_source(3alleg5)
β¨ NAME β¨
al_get_touch_input_mouse_emulation_event_source β Allegro 5 API π
(yes bestie, it's in the Allegro 5 manual, we're being β¨officialβ¨ today)
πΈ SYNOPSIS πΈ
#include <allegro5/allegro.h>
ALLEGRO_EVENT_SOURCE *al_get_touch_input_mouse_emulation_event_source(void)
π¦ DESCRIPTION π¦
Okay so picture this: touch screens, right? And mice? Two different little guys. Well, this function hands you back the global touch input event source β the one for emulated mouse events. π
And what does that event source do, you ask? It generates [emulated mouse events]ALLEGRO_EVENT_MOUSE_AXES(3alleg5) β and those events are based on touch events. So the touches are out here cosplaying as mouse movements, no cap. π
Heads up bestie: this is an [Unstable API] and it seems of limited value, as touch input tends to have different semantics compared to mouse input. Likeβ¦ the Allegro docs themselves are side-eyeing it a lil bit. π Not me calling out the API, but fr fr, touch and mouse are just built different.
π SEE ALSO π
β SINCE β
5.1.0 β she's been around since 5.1.0, an icon, a legend, and she is the moment. π«Ά
And that's the whole page, bestie! This was from the <strong>Allegro reference manual</strong>, for <code>al_get_touch_...n_event_source(3alleg5)</code>. Mwah, go forth and register 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