Magic Cube

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!)...

Fix for the next crasher from the field.

Adjust the app to match the changes in library.

Looks like we'll have to add 1 dim to the GLOW effect.

Remove the 'touchscreen required = false' from the manifest (because or a bug in Samsung App Store - it marks such apps as incompatible with any device)

One more fix for the latest bug from the field with Play state Spinner.

- bump version to 1.1.2
- fix one crasher observed in the field ( we need to adjust the Levels Spinner in Play state if Object changed in Pattern or Solver states )

Fix clicking on the 'Distorted.org' link; get app version from build.gradle (and not from strings.xml)

Add Crashlytics logs

Fix for the previous fix :)

Fix a potential crasher ( do not set up a callback for end of rotation effect on the very first cubit that belongs to a rotation if all belonging cubits have not been set up yet )