Re: Sluggish on Mobile Device

> On 2 Aug 2017, at 1:10 pm, Sannyasin Brahmanathaswami via use-livecode > wrote: > > Ahhh, I wonder if we only had two groups like this > > card "portal" > group "SivaSiva Portal Scrolling" # this is the group that scrolls very > badly no matter what we

Re: Sluggish on Mobile Device

@ monte: Elanor has the project link to our app on Git Hub if you are interested. I was going to submit a business support request to have your team examine that stack and see if there was a way to optimze it but I think Jacque has the bottom line: the "Siva-Siva-Portal.livecode" stack is

Re: Sluggish on Mobile Device

On 7/29/17 11:02 PM, Mark Waddingham via use-livecode wrote: It sounds like *something* in the group structure is causing accelRendering not to be effective (although I'm not sure what from the description). @Mark: I've just found why it's failing. It's the stack structure, not the engine.

Re: Sluggish on Mobile Device

On 7/29/17 11:02 PM, Mark Waddingham via use-livecode wrote: On 2017-07-30 05:43, J. Landman Gay via use-livecode wrote: There may be a minor difference when acceleratedRendering is on, but not enough to really help much. I'll see if I can extract a group. It's one from Swami's project, built

Re: Sluggish on Mobile Device

On 2017-07-30 05:43, J. Landman Gay via use-livecode wrote: There may be a minor difference when acceleratedRendering is on, but not enough to really help much. I'll see if I can extract a group. It's one from Swami's project, built dynamically, and all the images are referenced, so it isn't as

Re: Sluggish on Mobile Device

There may be a minor difference when acceleratedRendering is on, but not enough to really help much. I'll see if I can extract a group. It's one from Swami's project, built dynamically, and all the images are referenced, so it isn't as easy as just copying a card. Would referenced images

Re: Sluggish on Mobile Device

H - do you notice a difference between accelrender on and off on android? If you can copy the group onto a bare stack as is and file it with a bug report we can take a look. That case should work well so there might be something specific going on in that case. Warmest Regards, Mark. Sent

Re: Sluggish on Mobile Device

On 7/29/17 8:07 PM, Mark Waddingham via use-livecode wrote: So if you have a completely static scrolling group (i.e. one you can layout 'ahead of time' or build 'ahead of time') which can fit within a groups 32k co-ord width/height limit - then acceleratedRendering will do you just fine as

Re: Sluggish on Mobile Device

On 2017-07-30 02:35, J. Landman Gay via use-livecode wrote: Isn't this the "datagrid scrolling" issue we just funded? The layout has groups inside a container group. No - not quite. From what Dan said - he has a *fixed* layout - i.e. a group with 200 subgroups. Todd has used this approach

Re: Sluggish on Mobile Device

Isn't this the "datagrid scrolling" issue we just funded? The layout has groups inside a container group. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On July 29, 2017 6:28:06 PM Mark Waddingham via

Re: Sluggish on Mobile Device

So - quick outline... Set the layermode of the group to scrolling. Make sure it is just a bare group - no scrollbars, no border. Set the layermode of the other controls to static. Set the acceleratedRendering of the stack to true. Hopefully that should have some effect. Warmest Regards,

Re: Sluggish on Mobile Device

Sorry - I mean did you set the accelerated rendering to true? Sent from my iPhone > On Jul 29, 2017, at 7:20 PM, jonathandly...@gmail.com wrote: > > Did you set the acceleratedrendering of the group ? > > Sent from my iPhone > >> On Jul 29, 2017, at 5:59 PM, Dan Friedman via use-livecode >>

Re: Sluggish on Mobile Device

Did you set the acceleratedrendering of the group ? Sent from my iPhone > On Jul 29, 2017, at 5:59 PM, Dan Friedman via use-livecode > wrote: > > I have a stack/card that has: > > (1) A background that is a high-res image, > (2) A group of about 200 groups that