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 running. The engine uses these idle periods to do housekeeping, 
which I guess you could think of as "catching up."


When you wait with messages, the engine is put into the state where 
"nothing is happening" and so receives idle messages for the period of 
time specified by the wait. It also allows other user actions to execute 
and regular engine messages to be sent normally.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 time we want use it… perhaps 
what works is

1) finish all inits
2) set acceleratedRendering to true at the same time we create our mobile 
scroller
3) set it to false the same time we delete all our mobile controls

if this actually works, then we can just add this to our 
lib_mobileControls.livecodescript "backscript" and it would serve us everywhere 
in all contexts.  Just have to be careful not to be creating any scroller 
inside any *open* handlers.

worth a try. Though I expect Jacque may jump in with more caveats.

Also I believe the "wait with messages"  in effect creates a condition where 
"the app comes to an idle"  Though I'm still not clear on this, Jacque 
explained it briefly once, but going back to the dictionary, even reading the 
entry for wait very carefully.  "wait" shows "idle" as related and "idle" shows 
"wait" as related, but neither indicate exactly what that means.

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" ?? The current 
understanding seems to be that Livecode can "get ahead" of the OS on Android… I 
mean, any app is in effect a "controller" of the OS on the machine. So it's as 
if we have to let Android catch up before doing anything more? sheer guess work 
on my part… Mark would have a better analysis.  But we are seeing another bug 
"resume on Android causes LC to crash" seems to be alleviated if you the stack 
that has a wait handle in the preopenstack handler…so I guess on Android, open 
handlers are firing on resume, even though it appears that you are going and 
coming from an already open stack… another mystery there.

Until this bug (if it is one, since it works fine in iOS I presume it is) is 
fixed, a precise definition of the "best hackaround" in any context will be 
useful, so you are getting close to that.

BR



 

On 9/23/17, 5:21 AM, "use-livecode on behalf of Dan Friedman via use-livecode" 
 wrote:

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 – basically when 
the app comes to an idle) the acceleratedRendering then was enabled 
successfully and seemed to work properly from that point on.

That’s my 2 cents.  Hope it helps.

-Dan



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 – basically when 
the app comes to an idle) the acceleratedRendering then was enabled 
successfully and seemed to work properly from that point on.

That’s my 2 cents.  Hope it helps.

-Dan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 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.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 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 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 acceleratedRendering of this stack to "true"
end preopenstack

The "wait" was to fix something else, but I wonder if it is allowing
acceleratedRendering to kick in too. That would seem similar to your
suggestion to send the message in time.


On 9/21/17 12:48 PM, J. Landman Gay via use-livecode wrote:


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 it loads on preOpenCard or
preOpenStack. I guess I should poke around and see where those cards are so
I can test it again for you.

On 9/20/17 5:04 PM, panagiotis merakos via use-livecode wrote:


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 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 acceleratedRendering of this stack to true
end openStack


This results in black screen when the app starts.


Workaround:

on openStack
 send "fixit" to me in 0 millisec
end openStack

on fixit
 set the acceleratedRendering of this stack to true
end fixit

I'll file a report soon.

Hope this helps,
Panos



--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 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 acceleratedRendering of this stack to "true"
> end preopenstack
>
> The "wait" was to fix something else, but I wonder if it is allowing
> acceleratedRendering to kick in too. That would seem similar to your
> suggestion to send the message in time.
>
>
> On 9/21/17 12:48 PM, J. Landman Gay via use-livecode wrote:
>
>> 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 it loads on preOpenCard or
>> preOpenStack. I guess I should poke around and see where those cards are so
>> I can test it again for you.
>>
>> On 9/20/17 5:04 PM, panagiotis merakos via use-livecode wrote:
>>
>>> 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 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 acceleratedRendering of this stack to true
> end openStack
>
>
> This results in black screen when the app starts.
>
>
> Workaround:
>
> on openStack
> send "fixit" to me in 0 millisec
> end openStack
>
> on fixit
> set the acceleratedRendering of this stack to true
> end fixit
>
> I'll file a report soon.
>
> Hope this helps,
> Panos
> —
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
 --
 Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software   | http://www.hyperactivesw.com


 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode

>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>>
>>
>>
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 acceleratedRendering of this stack to "true"
end preopenstack

The "wait" was to fix something else, but I wonder if it is allowing 
acceleratedRendering to kick in too. That would seem similar to your 
suggestion to send the message in time.


On 9/21/17 12:48 PM, J. Landman Gay via use-livecode wrote:
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 it loads on preOpenCard or 
preOpenStack. I guess I should poke around and see where those cards are 
so I can test it again for you.


On 9/20/17 5:04 PM, panagiotis merakos via use-livecode wrote:

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 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 acceleratedRendering of this stack to true
end openStack


This results in black screen when the app starts.


Workaround:

on openStack
    send "fixit" to me in 0 millisec
end openStack

on fixit
    set the acceleratedRendering of this stack to true
end fixit

I'll file a report soon.

Hope this helps,
Panos
—
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode







--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 it loads on preOpenCard or 
preOpenStack. I guess I should poke around and see where those cards are 
so I can test it again for you.


On 9/20/17 5:04 PM, panagiotis merakos via use-livecode wrote:

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 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 acceleratedRendering of this stack to true
end openStack


This results in black screen when the app starts.


Workaround:

on openStack
send "fixit" to me in 0 millisec
end openStack

on fixit
set the acceleratedRendering of this stack to true
end fixit

I'll file a report soon.

Hope this helps,
Panos
—
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 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 acceleratedRendering of this stack to true
>> end openStack
>>
>>
>> This results in black screen when the app starts.
>>
>>
>> Workaround:
>>
>> on openStack
>>send "fixit" to me in 0 millisec
>> end openStack
>>
>> on fixit
>>set the acceleratedRendering of this stack to true
>> end fixit
>>
>> I'll file a report soon.
>>
>> Hope this helps,
>> Panos
>> —
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>>
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

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 acceleratedRendering of this stack to true
end openStack


This results in black screen when the app starts.


Workaround:

on openStack
   send "fixit" to me in 0 millisec
end openStack

on fixit
   set the acceleratedRendering of this stack to true
end fixit

I'll file a report soon.

Hope this helps,
Panos
—
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode