Skeleton Cube2 tablebases class.
Bugfix.
2x2 solver class finished.
Beginnings of the 2x2 solver.
Dialog About.
New MrUK tutorials.
What's New.
Icosamate: mesh, jsons.
first attempt at Icosamatenew PL tutorial for the Crazy Planets
Move corner orientation from SolverPyraminx to TablebasesPyraminx (we'll need it for better-looking tablebases scrambling)
Tablebase-based scrambling.
Close assets after use.
Minor
Introduce InitAssets. We'll use this later to pass on references to the tablebase file to the TwistyObject (so that it can use this for perfect scrambling)
Up version to 1.12.4, what's new.
Add skeletons of the Cube2 & Skewb solvers.
Diamond Skewb solver: add Tablebase.
Diamond Skewb solver should be fully working now.
Progress with the Diamond Skewb solver.
New button in the solver screen: reset all textures.
Progress with Skewb Diamond solver.
Solver: new error strings.
Beginnings of Skewb Diamond solver.
Pyraminx solver: bugfix.
Pyraminx solver: add tips.
Pyraminx solver: tablebase working now (tipless, tips to be added in the SolverPyraminx class)
Pyraminx solver: progress
Pyraminx solver: error messages
CU_232 solver: filtering the position should work now
More translations for the CU_232 solver
Beginnings of the 2x2x3 solver.
What's new
Ivy solver finished
Small corrections
Correct Ivy's order of cubits.
Ivy Solver: implementations of getIndex() and getQuats() remain.
Introduce ImplementedTablebasesList
Fx the solver to be able to handle the case when someone repainted the faces in a different order
Read TB from file.
Pyraminx Duo solver: solutions (coming from unpacked DB recreated each time) seem to be working.
Pyraminx Duo solver: initial code which creates the unpacked DB (does not work still)
Pyraminx Duo solver: initial error cases should be finished.
Remember last solver type in preferences.
Progress with the Pyraminx Duo solver
Progress with PDuo solver
- add the Pyraminx Duo solver to the list- make the signature of an object independent of its location in the ObjectType enum
Beginnings of the Pyraminx Duo solver.
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: improvements.Remove the About dialog.
Solvers dialog: improvements.
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.
'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....
Introduce RubikDialogSolvers.
Unify all dialogs.
Continue unifying all the dialogs under one RubikDialogAbstract.
Start unifying all the dialogs under one RubikDialogAbstract.
Support RTL in Bandaged Creator Activity.
More fixes for UI in case of extreme screen (w/h) ratios ( from 1.0 to 2.0 ).
Move the control of object scaling out the objectlib.Thee xact way the object is scaled needs to be decided in the app, as only the app knows that e.g. in the Rubik main screen, if it is a square, then obejct needs to be a bit smaller than in case of Config screen (if that one happens to be a square)
TutorialActivity: link to PurchaseActivity.