samples/Grapefrukt: USING “SENSOR-LANDSCAPE” ORIENTATION FOR ANDROID (SEEMS TO PERFORM AS INTENDED ON SEVERAL DEVICES SO FAR)
ANDROID LIFECYCLE REWORK: SIMPLIFICATION
ANDROID LIFECYCLE REWORK: MORE SIMPLIFICATION
ANDROID LIFECYCLE REWORK: TESTING GLView SHOW/HIDE
ANDROID LIFECYCLE REWORK: GLView SHOW/HIDE SEEMS TO WORK AS INTENDED (TESTED ON NEXUS 7 2013 V4.2.2)
ANDROID LIFECYCLE REWORK: TESTING GLView ATTACH/DETACH. PROBLEM: GLSurfaceView’S DESIGN DO NOT ALLOW TO NOTIFY THE RENDERER’S THREAD UPON DETACHMENT
ANDROID LIFECYCLE REWORK: GLView SHOW/HIDE: ADDING SOME ROBUSTNESS (E.G. APP IS STARTED WHILE GLView IS HIDDEN, ETC.)
ANDROID LIFECYCLE REWORK: NEW FINDINGS: “DEFORMATION BUG” IS PROPERLY HANDLED *ONLY* WHEN GLView IS ADDED VIA Activity.setContentView()
ANDROID LIFECYCLE REWORK: NOW SUPPORTING “GL CONTEXT PRESERVATION” (WHILE NOT FULLY TRUSTING IT) — WORKS ON NEXUS 7 2013 (V4.2.2) — TODO: TEST ON MORE DEVICES
ANDROID LIFECYCLE REWORK: SIMPLIFICATION + THE “DEFORMED SCREEN” PROBLEM WAS ACTUALLY RELATED TO glViewport! SEE COMMENT IN GLRenderer.onSurfaceChanged()
ANDROID LIFECYCLE REWORK: HANDLING GLRenderer.onSurfaceChanged() PROPERLY, I.E. IN A WAY THAT ALLOW USERS TO CALL THEIR OWN glViewport() OPERATIONS WITHIN THE resize CALLBACK
ANDROID LIFECYCLE REWORK: INVOKING GLRenderer.launch() WHEN THE RENDERER’S THREAD STARTS (I.E. REGARDLESS OF THE GLView’S VISIBILITY…)
ANDROID LIFECYCLE REWORK: INTRODUCING Uitls.LOGD, ETC.
ANDROID LIFECYCLE REWORK: TESTING GrapeFrukt’s BridgeActivity WITH GLView ON TOP OF AN ANDROID VIEW, AND HIDDEN OR DETACHED AT APPLICATION START.
EVERYTHING WORKS AS INTENDED, EXCEPT THAT GLRenderer.onDetachedFromWindow() CAN’T BE REACHED, AS EXPLAINED IN GLView.onDetachedFromWindow()
ANDROID LIFECYCLE REWORK: FINALLY CAPABLE TO COMMUNICATE WITH THE RENDERER’S THREAD WHEN THE GLView IS DETACHED!
ANDROID LIFECYCLE REWORK: UI ENHANCEMENTS IN GrapeFrukt’S BridgeActivity + INTENSIVE HIDE/UNHIDE AND ATTACH/DETACH TESTS (STILL HESITATING WHETHER ALLOWING GLVIew RE-ATTACHING…)
ANDROID LIFECYCLE REWORK: FIXING GLRenderer.onDestroy (SEE TODO REGARDING forceDestroyOnDetach) IN GLView. TESTED ON Scalability SAMPLES, SINCE THE BACK-BUTTON IS CURRENTLY BROKEN IN GrapeFrukt
ANDROID LIFECYCLE REWORK: ADDING THE CAPABILITY TO DIFFERENTIATE BETWEEN AN onPause EVENTS (WHETER ACTIVITY IS GOING TO BACKGROUND OR IT IS DESTROYED…)
ANDROID LIFECYCLE REWORK: NOT RELYING ON Activity.onDestroy() ANYMORE AND CALLING GLRenderer.onDetachedFromWindow() (INSTEAD OF onPause()) WHEN APPLICATION IS DESTROYED
ANDROID LIFECYCLE REWORK: INTRODUCING GLView.destroyOnDetach(), WHICH IS TRUE BY DEFAULT (TODO: TRY TO DISABLE GLView REUSE AFTER DETACHMENT…)