Make it possible to return rowBitmaps from ObjectScrambler (rather than single rows)
Tablebase-based scrambling.
New button in the solver screen: reset all textures.
Win effects: first remove all effects, only then inform the Listener the whole Win sequence finished.
IAP: finish the 'Purschase' activity.
IAP part 6: new 'Present' object effect (cont'd)
IAP part 6: new 'Present' object effect.
Important bugfix for fast scrambling!
scramble,solve,win: license.
effects,fastscramble,objectchange: license.
Make the fastScramble incremental.
Make the BandagedPlay use FastScramble. (static 500 times)
Implement the FastScramble effect.
- move the 'object' popup to the botton right- move the 'solve' button to the upper left- movee the 'scramble' button to the upper right (its new FastScrambleEffect still not implemented fully)
Preparation for Mixup Cube: take advantage of the recent bump in MAJOR_VERSION number and change the format of basicAngles to int[][] 'per-axis-per-layer' [ Mixup Cube has different basicAngle in its middle layers (8) - and different in its edge layers (4) ]
Cleanups.
Convert Ulti, Jing, Pyra, Diamond, Dinos, Redi, Skewbs, Ivy & Rex to the new scheme where the quaternion group is computed automatically.
Minor.
Fix setDefaultRotation() when changing an object; do it at exactly the right time when the 'old' object has already disappeared, but the new hasn't been attached to the Nodee yet.
Fix problems with TwistyObjectNode 'object scale' property.Now this property is not part of the Node at all, but its initial value passed to the object in its constructor.
Further simplify ObjectType
Major change: separate the notion of a TwistyObject and its Node. Now,
1) the Node stays when we change objects (this makes transitions faster)2) it's possible to just create an Object without adding it to the Screen (now app needs to explicitly create the Node and add it to its Screen itself)
- remove the retarded NODE_RATIO from TwistyObject- more correctly estimate Cuboid's 'realSize' as an average of their 3 sizes.
Relax objectlib's requirements: it can be displayed not only on top of a DistortedScreen, but any DistortedFramebuffer.
No, move the object afterall. Why? See in Tutorials - a moved node has the right side missing.
Improve 'off-center' objects: move the node, not the object!This simplifies the Effects and makes them more correct (glow!)
off-center objects: finished.
progress with off-center objects.
1) introduce possibility to move objects, i.e. display them not in the middle of the screen (not fully functional yet)2) do away with unneeded any more interface 'EffectController' - since ObjectPreRender is the only implementation now.
Remove the 'setupObject()' redundant API.
Bugfix: we shouldn't be calling TwsityObject.solve() directly from the app, only through ObjectControl.solveOnly().
Simplifications
Move yet more code to objectlib.