Magic Cube

Add of flag of Tanzania!

Only show the OpenGL Error dialog when the underlying hardwarre does not support OpenGL ES 3.0.

Add OpenGL Error dialog.

Progress making it possible to apply Vertex Effects only to some Components of a Mesh.

Correct a crasher introduced in 1.2.0

Switch off showing FPS.

Report an Analytics event when a user changes State or Object.

Report a Crashlytics non-fatal if we fail to compile some shaders.

Hopefully get rid of the most common crash in the field right now by changing the States to always create all their Views from scratch.

Bump version to 1.2.0

1) Cube: convert it to the latest library. Main difference: objects are rendered better, individual cubits have rounded corners.
2) Examples: some adjustments to MeshJoin & Predeform
3) Library: fix a bug in main_vertex_shader's 'degree' function, which didn't work proprely in case of a vertex which was exactly at the center (i.e. vector PS was zero)

In library: allow a mixture of a deep and shallow copy of a Mesh ( mVertAttribs1 might be copied deeply or shallowly, mVertAttribs2 are always copied deeeply).
Port RubikCube to the new library.

correct Qatar flag & add Trynidad flag.

We have

- three bugfixes for crashers as seen in Firebase
 - one fix for a nasty logic error
 - improvements to the Scores Dialog
 - new Ivory Coast flag :)

so it's time for 1.1.4

Fix a nasty logic error that let people submit bogus results.

Fix for the next crash seen in the field.

Fix for a crasher seen in the field.

Minor.

Improve the way we fill up the Scores tab - now it follows what user's doing, so if he changes tabs when the dialog is filling up, he won't have to wait so long.

Add Ivory Coast flag.

Smaller halo.

Again we have 2 bugfixes for crashers seen in the field and updated zh-CN and zh-TW translations.
Bump version to 1.1.3 then.

New Traditional and Simplified Chinese translations.

Fix for another crasher from the field.

Change the Postprocessing effects: separate the radius and the halo.
Reason: we needed a way to specify the size of the halo around a postprocessed object; before it was automatically (and not very correctly) computed from the radius - before we knew the size of the object's bounding box, so this automatic computation was possible. Now we're removing the MashBase.getBounding(0 API, so the size of the halo has to be explicitly given by the user. This way is more correct anyway and gives the user more control (as the Multiblur app proves!)...