ALLEGRO_MO...ATION_MODE(3)

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

πŸ’… ALLEGRO_MO...ATION_MODE(3) πŸ’…

okay bestie, this one is straight out of the Allegro reference manual / Library Functions Manual, and it’s giving Allegro 5 API energy. It’s a typedef enum situation for choosing how mouse emulation gets applied. 🐭✨


🌸 NAME 🌸

ALLEGRO_MOUSE_EMULATION_MODE β€” Allegro 5 API. That’s the enum name, no cap.

πŸ¦‹ SYNOPSIS πŸ¦‹

#include <allegro5/allegro.h>

typedef enum ALLEGRO_MOUSE_EMULATION_MODE

πŸŽ€ DESCRIPTION πŸŽ€

Type of mouse emulation to apply. That’s the whole vibe: you pick one of these enum values.

  • ALLEGRO_MOUSE_EMULATION_NONE β€” Disables mouse emulation. Nope, no emulation here.
  • ALLEGRO_MOUSE_EMULATION_TRANSPARENT β€” Enables transparent mouse emulation. See-through emulation vibes.
  • ALLEGRO_MOUSE_EMULATION_INCLUSIVE β€” Enable inclusive mouse emulation. Inclusive mode is on the menu.
  • ALLEGRO_MOUSE_EMULATION_EXCLUSIVE β€” Enables exclusive mouse emulation. Exclusive mode, very main character.
  • ALLEGRO_MOUSE_EMULATION_5_0_x β€” Enables mouse emulation that is backwards compatible with Allegro 5.0.x. It’s for the 5.0.x girlies. πŸ’Ύ

⭐ SINCE ⭐

5.1.0. Periodt.

[Unstable API]: Seems of limited value, as touch input tends to have different semantics compared to mouse input. Bestie, that’s the official warning β€” touch input is a different vibe from mouse input, so this API is marked unstable and seems of limited value. πŸ’€

Cute sign-off: source/version is the Allegro reference manual, the page footer says ALLEGRO_MO...ATION_MODE(3), and there’s no date shown on that footer β€” so we’re not inventing one. Love that for us. πŸ’–πŸ«Ά

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