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
Minor
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: 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....
Introduce RubikDialogSolvers.
Change the '3x3x3 solver' string.
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.
Block rotating layes of not free objects in the Tutorial Activity.
Further improvements for the UI.
Improve UI proportions on squarish screens.
Convert 'buy whole app' to 'buy all puzzles'
Add Stars to the main menu.
Progress with 'Stars' dialog.
Released 1.11.6 version
Records dialog: support objects with less than 8 number of scrambles.
Make it possible to decide about FastScramble duration fromo outside the ObjectControl.
SetName dialog can become entangled in exceptions...
Make several objects built-inoone fix for USE_IAP
Dialog 'buy stars'
Unlock downloaded objects on download if we have everything in the app unlocked!
Very important bugfix for an issue which probably has been the reason for many mysterious behaviours in the past: the JsonReader class cannot be a singleton! Convert it into a normal 'instanced' class.With it being a singleton there's a major issue: when we create a new TwistyObject from a JSON file (by, for example, going to PurchaseActivity) and then we come back to the old object (by, for example, going back to the main RubikActivity) - then the JsonReader inside the old object has read the new JSON file and thus many of the 'abstract' methods in the old TwistyObject (for example getShortName()) all of the sudden start returning new values!
Purchase Pane: further progress.
Purchase Pane: post-purchase dialogs.
Purchase Pane: buttons (part2)
Purchase Pane: buttons
Purchase Pane: resources.
Fix marking objects as free.
Merge remote-tracking branch 'origin/master'
Bugfix: properly display number of stars on new installs.
Stars dialog: chinese translations.
fix showing the number of stars on app startup.
improve the stars dialog.
Stars: introductory dialog explaining the concept of stars.
Stars Overlay: fix the 'negative numbers of new stars' mode.
Stars Overlay: implement zero and negative numbers of new stars.
Changes to the initialization - initialize the 'bought objects'
correct the stars animation.corect number of stars earned in level 8.
'Stars' animation: support totalStars up to 5 digits long, i.e. up to 99999.
Now the 'stars' animation should fulling work, even on the physical LG phone.
Stars animation: looks like if we do not switch off the depthMask and stencilMask of the OverlayNode, then the crash on my physical LG phone goes away.
Stars animation: support spending stars.
make the little flying stars disappear in the end.
The 'stars earned' effect is done. Works only for newStars>0.Also, there is a crash in the graphics driver on my physical LG phone.
Progress with Masterball TouchControl.
Interface: properly support object which have numScrambles less than 8.
Report number of stars to the server.
All users who are upgrading from a version <1.11.4, where there was no concept of 'stars', get all their stars.