Optimizing for small Android devices

J. Landman Gay jacque at hyperactivesw.com
Sat Dec 30 20:22:05 EST 2017

On 12/30/17 2:44 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
> I think we need to wait until HQ weighs in on my bug report. Regardless of the fact that it works on iOS and Oreo, one has to wonder how on earth we can close a stack which is set to destroy on close, turn acceleratedRendering to false (assume previously cached controls are  cleared); open a new stack and*still*  see the old stack behind the new, one, as if they two are still fighting for the pixel map…. even if the old one "loses" on iOS and Oreo…and the new stack "wins" the display.. .the old one could still be in the heap.

This could be a redraw issue rather than an open stack, but see what HQ 
says. I know that pixels outside the card area aren't redrawn on mobile, 
this could be related.

Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com

More information about the use-livecode mailing list