Whats new
Workaround (real reason not found) for the issue when furious touching the screen in the BandagedCreator could sometimes leave a cubit permanently lit.
Bugfixes for touch control - specifically for furious swiping and concurrect backing of moves.
Bugfix for the Scores dialog.
Bump to 1.12.2
Up version to 1.12.1
Unblock PreRender's scrambling & solving oonly AFTER we change screen to READ post-scrambling (otherwise it was possible to press the 'solve' button in the brief period between unblocking and switching screen because switching screen runs on the background UI thread)
Minor.
calls to FastScramble and SlowScramble might fail (preRender is blocked). Return false then and if so, do not do anything in the app.
What's New dialog: translations.
What's New dialog: improvements.Remove the About dialog.
Solvers dialog: improvements.
Solvers dialog: translate contents.
Block the object, menu & back moves while we're scrambling!
Fix a bug with level buttons in objects with less than 9 numScramble.
Progress with the Camouflage 3x3x3.
Bugfix.
'What's new' UI.
What's new dialogBump version to 1.12.0
UI iimprovements inthe Solver screen.
Remove the 'switchTouchControl' optimization which, with many different objects in the solver screen now, does not work any more.
Progress with SolverScreen.
Progress with solvers dialog.
Some improvements to blocking, mostly to the names of variables.
Finally fix the 'impossible records' bug!
Thanks for a bug report from Jacob Powell - if one, during scrambling, minimized the app and re-entered it, the UI lock got removed (by a call to 'unblockEverything' from RubikActivity's onResume) and one could then keep solving the object mid-scramble....
Also available in: Atom