Re: Setting the acceleratedRendering to true on startup on

2017-09-23 Thread J. Landman Gay via use-livecode
On 9/23/17 2:27 PM, Sannyasin Brahmanathaswami via use-livecode wrote: when we issue "wait 200 milliseconds with messages" does the engine send idle to the card? i.e now the phone OS has time to "catch up" ?? Basically. The idle message is sent regularly whenever no other handlers are

Re: Setting the acceleratedRendering to true on startup on

2017-09-23 Thread Sannyasin Brahmanathaswami via use-livecode
Dan, yes this could be really helpful Almost all (but one) use cases in our app framework are simply to facilitate either a scrolling field or a scrolling group. If we are looking for some consistent "algorithm" for this, which I am, so we don't have so much mental-re-estate consumed every

Re: Setting the acceleratedRendering to true on startup on

2017-09-23 Thread Dan Friedman via use-livecode
I had these exact same issues: black screen if acceleratedRendering was enabled on Android at startup. I found that if I set the acceleratedRendering to true after ALL startup items were complete (preOpenCard, preOpenStack, openCard, openStack, and whatever else you’re doing at launch –

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-22 Thread Sannyasin Brahmanathaswami via use-livecode
Not only that… but I think we have other stacks where the wait is applied before accelerated rendering and it is stills stopping on exit/resume. I'm deep into refactoring… will get around to deploy again on devices in a day or so… will report back again then. J. Landman wrote: It's kind

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-22 Thread J. Landman Gay via use-livecode
It's kind of odd though, because the wait occurs before acceleratedRendering is set. I'm not sure how a prior wait could affect a command that hasn't happened yet. On 9/22/17 2:20 PM, panagiotis merakos via use-livecode wrote: Hi Jacque, Thanks for checking. Yes, it seems that the "wait" is

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-22 Thread panagiotis merakos via use-livecode
Hi Jacque, Thanks for checking. Yes, it seems that the "wait" is probably fixing things here. I also tested on a Pixel running Oreo. Best regards, Panos -- On Fri, Sep 22, 2017 at 7:48 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > Panos: I just tested Swami's

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-22 Thread J. Landman Gay via use-livecode
Panos: I just tested Swami's app on my Pixel running Oreo (Android 8) and acceleratedRendering seems to be working okay. There is a preOpenStack handler in the stack script: on preopenstack wait 100 milliseconds with messages set the fullScreenMode of this stack to "ShowAll" set the

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-21 Thread J. Landman Gay via use-livecode
I have a Pixel that was just updated to Oreo (Android 8) and running Swami's app works okay. That's the one app I happen to have installed that uses acceleratedRendering quite a bit. He's made some changes recently that turns it on and off after the card has already loaded, but on some cards

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-20 Thread panagiotis merakos via use-livecode
Hi Jacque, Are you on Android 7 or 8? It does not work for me if I set the acceleratedRendering in preopenstack or openstack. I did not check with opencard/preopencard. On Wed, Sep 20, 2017 at 10:13 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > Does it work if

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

2017-09-20 Thread J. Landman Gay via use-livecode
Does it work if you set acceleratedRendering in preOpenStack or preOpenCard? It seems to work okay for me that way. On 9/20/17 5:21 AM, panagiotis merakos via use-livecode wrote: Hi folks, Today I came across this issue, affecting Android 7 and Android 8: on openStack set the