AL_RECONFIGURE_JOYSTICKS(3)

💖 NAME 💖

Hey bestie, welcome to al_reconfigure_joysticks(3) — brought to you by the Library Functions Manual. This one is al_reconfigure_joysticks, aka the Allegro 5 API glow-up for your joystick lineup 💅

---

🎀 SYNOPSIS 🎀

#include <allegro5/allegro.h>

bool al_reconfigure_joysticks(void)

---

🌸 DESCRIPTION 🌸

Okay so Allegro is built to cope with users plugging in and unplugging joystick devices on-the-fly — yes, while everything is running, no big production. On existing platforms, the joystick event source will generate an event of type ALLEGRO_EVENT_JOYSTICK_CONFIGURATION when a device gets plugged in or unplugged. When that happens, your move is to call al_reconfigure_joysticks(3). That's the assignment 💖

Afterwards, the number returned by al_get_num_joysticks(3) may be different, and the handles returned by al_get_joystick(3) may be different or be ordered differently. So if the lineup shuffled, that's expected — no cap.

All ALLEGRO_JOYSTICK(3) handles remain valid, but handles for disconnected devices become inactive: their states will no longer update, and al_get_joystick(3) will not return the handle. Handles for devices which remain connected will continue to represent the same devices. Previously inactive handles may become active again, being reused to represent newly connected devices. Reuse era, honestly.

Returns true if the joystick configuration changed, otherwise returns false. Literally the vibe check of return values ✨

It is possible that on some systems, Allegro won’t be able to generate ALLEGRO_EVENT_JOYSTICK_CONFIGURATION events. If your game has an input configuration screen or similar, you may wish to call al_reconfigure_joysticks(3) when entering that screen. Little safety-net behavior, iykyk 🫶

---

🦋 SEE ALSO 🦋

• al_get_joystick_event_source(3)
• ALLEGRO_EVENT(3)

---

That's the whole tea, bestie 🍓 — source: the Allegro reference manual, and this page is undated, so she's giving timeless icon energy, periodt 💅✨