AL_GET_TOUCH_INPUT_STATE(3)

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

πŸ’… al_get_touch_input_state(3) β€” Allegro 5 API touch-state moment ✨

Manual name: Library Functions Manual β€” folded in near the top, cute and accounted for. πŸŽ€ This is the Allegro 5 API page for grabbing the current touch input state, and it’s lowkey a one-function wonder. πŸ¦‹


🌸 NAME 🌸

  • al_get_touch_input_state β€” Allegro 5 API. That’s the whole name, bestie; no cap. πŸ’–

✨ SYNOPSIS ✨

Include this header:

#include <allegro5/allegro.h>

Then the function signature is exactly:

void al_get_touch_input_state(ALLEGRO_TOUCH_INPUT_STATE *ret_state)

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so what does it do? It gets the current touch input state β€” literally the touch vibe check at this exact moment. 🫢

The touch information is copied into the ALLEGRO_TOUCH_INPUT_STATE(3) you provide to this function. You hand it ret_state (that ALLEGRO_TOUCH_INPUT_STATE * from the synopsis), and boom: the current touch info lands in the ALLEGRO_TOUCH_INPUT_STATE(3) you gave it. πŸ’…

No cap: the copying destination is the ALLEGRO_TOUCH_INPUT_STATE(3) you pass in. That’s the whole flow. ✨

⭐ SINCE ⭐

Available since 5.1.0 β€” vintage Allegro 5 era, but make it iconic. πŸ‘‘


Sign-off era: πŸ“š source/version: Allegro reference manual Β· page: al_get_touch_input_state(3) Β· date: no date listed on this page, so I’m not inventing one, bestie. πŸ’œ

πŸ“¦ 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