Yes, i told we’d do bi-weekly releases from now on 🙂 Here’s what’s new!
- updated to RoboVM 0.12 (and so should you!)
- fixed GC issues on iOS with regards to touch (thanks Niklas!), see <a href="https://github.com/libgdx/libgdx/pull/1758">https://github.com/libgdx/libgdx/pull/1758</a>
- updated gwt gradle plugin to 0.4, android build tools to 0.10, gradle version to 1.11
- Tiled maps are now always y-up
- Tiled maps now support drawing offsets for tiles
- FileHandle#list is now supported in GWT!
- FileHandle#list now supports FileFilters
- Controllers now reinitialize on the desktop when switching between windowed/fullscreen
- added a Texture unpacker that will extract all images from a texture atlas, see <a href="https://github.com/libgdx/libgdx/pull/1774">https://github.com/libgdx/libgdx/pull/1774</a>
- updates to gdx-setup
- CustomCollisionDispatcher in bullet, see <a href="https://github.com/libgdx/libgdx/commit/916fc85cecf433c3461b458e00f8afc516ad21e3">https://github.com/libgdx/libgdx/commit/916fc85cecf433c3461b458e00f8afc516ad21e3</a>
Note: you’ll have to update to the latest RoboVM (0.12) and Android build tools (0.10) to use this new release!
Note: it takes a while for the new version to be synched to Maven Central (an hour or so). If you update your build.gradle or generate a new project with the latest gdx-setup.jar, the download of libGDX will fail until Maven Central has the JAR files. You can refresh this site every 2 seconds and ask “is it live yet?!”
There have been other fixes as well, you can follow the full commit history on GitHub.
We also wrote a guide on how to update/change the libGDX version your project uses. Please consult that one to update your 1.0.0 projects. It’s super easy.
Last note: look at the new version, it’s 1.0.1, that is we only updated the patch number. This means no API breaking happened, only API additions and/or bug fixes! This also means it is save for you to update your project from the previous version to the new version. If the new version would be 1.1.0 you’d know that a breaking API change was introduced, which we’d document in the release notes.
Funny bonus: i did a Hangout on Air that let’s you follow what goes into a release. It’s VERY long and boring, ymmv.