Alexandre Martins

This has been asked before, so I'll consider implementing this feature in a future version. It took me a ton of work to create the scripting engine, but now it's...

Some of my users have been reporting the same issue. I never heard of this lag back in the days of Allegro 4. This may indeed be related to hot...

> I'm not aware (although I'm not at all an expert) that DirectInput gives notifications of device changes - which presumably makes calling IDirectInput8_EnumDevices() regularly the only way of finding...

I think the same and I had the same idea. I'll leave this open for now.

> This isn't needed anymore now that #1483 is merged, right? I think that there is still a design issue that hasn't been addressed. If you agree, I would like...

Correction: `ALLEGRO_KEY_DPAD_*` are never triggered anywhere because D-Pad KeyEvents are mapped to `ALLEGRO_KEY_UP`, `ALLEGRO_KEY_DOWN`, `ALLEGRO_KEY_LEFT`, `ALLEGRO_KEY_RIGHT` and `ALLEGRO_KEY_ENTER` instead of their `ALLEGRO_KEY_DPAD_*` equivalents. Even though the `ALLEGRO_KEY_DPAD_*` keys are defined,...

Thank you for your response. If I may offer feedback, there seems to be a design issue. The Android game keys are actually gamepad buttons and the dpad keys are...

> This is probably the best option at this time (we can add an allegro5.cfg option to disable the old events). If I merge #1483 does this implement this or...

> I think the goal should be to get the Android joystick to be as good as possible, with all the keys mapped. The keyboard events should be left as...

> First, is consistent cross-platform mapping, which should be fixed, but out of scope here. Would you like it fixed at this time? A consistent mapping already exists for controllers...