Woohoo! It's been a little while since we released Allegro! This release as always was made possible by the hard efforts of our many amazing contributors, some new and some old. Many bugs were squashed, and many features were added. One particular feature I want to highlight is the new Android build system courtesy of Elias, which makes compiling Allegro for Android a cinch!

You can grab the source archives and MinGW packages here. The MinGW dependency packages have been updated to the newest versions of dependencies (not libwebp yet though), and I've tried to make the archive naming scheme be more useful.

MSVC packages are available on Nuget, and Ubuntu PPA and OSX homebrew will be updated in the coming days.

What are current changes / needs / milestones that people can help with to continue development?

Any addons? Modules? etc

I've considered writing a RawAPI driver for multiple mouse/keyboards in the past. I'd like to do a full API that decouples effectors (inputs) from their actions and allow changing things like applying function curves (change linear input to exponential or vice-versa), debouncing, etc. But that's a much bigger project and might be an external library that allows linking to Allegro (and other libs).

I use DAlleg. Anything added or tested you need with that, Siegelord?

-----sig:“Programs should be written for people to read, and only incidentally for machines to execute.” - Structure and Interpretation of Computer Programs

Chris Katko, see the mailing list for a small discussion of Multi mice/keyboard support. Basically you use the RawInput API on Windows and monitor all the HID devices attached. I wrote a program that does this, called ManyMouse, which you can view here :

If you don't mind, I think it would be nice for audio addon to have tempo change speed functionality in near future.

This is actually a pretty complex algorithm, while the simple speed manipulation is pretty trivial. I don't know if it can be done in a streaming fashion. Besides this, we'd need to figure out some API for this.

What are current changes / needs / milestones that people can help with to continue development?

In general, reducing the number of issues is something we work on, https://github.com/liballeg/allegro5/issues, we have a number of issues tagged 'Easy'. Overall, the input system could use a bit of work: on Windows we don't properly support IME, and on Linux we're not quite doing the right thing (https://github.com/liballeg/allegro5/issues/723). Also joystick support really could use a rework across all platforms. There are quite a few other longstanding issues as well.

jalleg binding library version is the same, only if you want to pull in a pre-built JAR that unpacks the DLL for you, you can use newer jalleg-rt. It'll be a couple of hours before the artifacts hit Maven Central.