On 2017-08-21 19:13, Jonathan Lynch via use-livecode wrote:
It is on iOS. Turning it on and off as needed has worked perfectly, so
it is no problem. Thanks for explaining!
Okay - so obviously it hasn't 'got any better' since iOS4 which was when
we added acceleratedRendering mode... This is sli
It is on iOS. Turning it on and off as needed has worked perfectly, so it is no
problem. Thanks for explaining!
Sent from my iPhone
> On Aug 21, 2017, at 12:54 PM, Mark Waddingham via use-livecode
> wrote:
>
>> On 2017-08-21 18:51, Jonathan Lynch via use-livecode wrote:
>> Hi Bob- I can repor
On 2017-08-21 18:51, Jonathan Lynch via use-livecode wrote:
Hi Bob- I can report that accelerated rendering "steals" resources
from the browser widget. I have to turn it off when displaying a 3D
map in the browser widget, then turn it back on for scrolling groups.
Otherwise, the map renders in a
On 2017-08-21 18:41, Bob Sneidar via use-livecode wrote:
Hi all.
Since acceleratedRendering is a stack property, does it only apply to
a given stack, and not, for example to a sub stack? What would the
advantage be of having it off? If none, why even have it?
It is per stack, and not inherited
Hi Bob- I can report that accelerated rendering "steals" resources from the
browser widget. I have to turn it off when displaying a 3D map in the browser
widget, then turn it back on for scrolling groups. Otherwise, the map renders
in a very clunky way, with large sections very distorted.
It ha
I meant to say, why not just have it on permanently?
Bob S
> On Aug 21, 2017, at 09:41 , Bob Sneidar via use-livecode
> wrote:
>
> Hi all.
>
> Since acceleratedRendering is a stack property, does it only apply to a given
> stack, and not, for example to a sub stack? What would the advantag
