Fix a long-standing buf in CubesGrid (incorrect Grid in case of 5x5 11111 11011 10101 11011 11111)
Chasing a bug in DistortedCubesGrid.markRegions() ( visible with a 5x5 grid, 11111 11011 10101 11011 11111 ) - some side edges are missing. markRegions computes incorrect number of side Segments in this case.
Various relatively minor cleanups.
1. (hopefully) finish the 'Save' app (now we can adjust the size of the resulting file)2. Fix one long-standing bug in almost every single app.
Move the 'Save' app to using a DistortedFramebuffer.
Improvements for DFramebuffer.
Fix the 'Save' app so that the saving thread does not run all the time in a tight loop
Javadoc
Fix with Projection
Turn the former 'FOV' app into 'Projection' app that also checks the (x,y) the camera looks at.
Move the *List classes into static members of DistortedFramebuffer and DistortedObject.
Cleanup
DistortedFramebuffer should we working now, including deletions.
Simplify SurfaceViews
Move DistortedNode and Distorted to use the new DistortedRenderTarget.
Minor progress with RenderTarget
New DistortedRenderTarget - preparation for being able to render to any FBO (screen, offscreen pixmaps)
Minor stuff
Fix the 'Save' app on Android API >=23 (we need to explicitly ask for write permission)
Also available in: Atom