In my case all groups that use a scroller have scrolling layermode set. They work. The primary problem for me is that regular LC controls stop getting messages and responding to taps.

All these controls are set to static layermode, so I'm not sure how acceleratedRendering could affect them. But it does bring the app to a screeching halt. I wish I had a recipe.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 2, 2020 8:35:49 PM scott--- via use-livecode <use-livecode@lists.runrev.com> wrote:

I had two different scrolling groups on a card where I found it necessary to toggling acceleratedRendering. I just discovered that neither of these groups had the layerMode set to “scrolling” (they were both “static”). Though they appeared to scroll smoothly on all my test devices, changing their layerModes to “scrolling” now makes it so the acceleratedRendering doesn’t need to be fiddled with in order for other objects to display correctly.
—
Scott

On Jun 2, 2020, at 5:55 PM, scott--- via use-livecode <use-livecode@lists.runrev.com> wrote:

Hello Randy,

Adjusting the compositorCacheLimit (instead of toggling the acceleratedRendering) also seems to fix my most recent encounter. It is good to have work-arounds but frustrating to have the issue crop up.

—
Scott

On Jun 2, 2020, at 5:20 AM, Randy Hengst via use-livecode <use-livecode@lists.runrev.com> wrote:

I have an iOS app that uses many graphics with movement… in addition to doing as Scott suggested (toggling acceleratedRendering on an off) I also messed with adjusting the compositorCacheLimit. Raising the limit helped. Doing this also helped with some screen redraw issues I saw that sounds consistent with what Scott also mentioned.


be well,
randy
www.classroomFocusedSoftware.com

On Jun 2, 2020, at 1:58 AM, J. Landman Gay via use-livecode <use-livecode@lists.runrev.com> wrote:

On 6/1/20 11:30 PM, Mark Wieder via use-livecode wrote:
On 6/1/20 9:15 PM, J. Landman Gay via use-livecode wrote:
Oh my gosh, I *never* would have guessed that fullscreenMode was the culprit. That's kind of screwy isn't it? Why would it block taps? And not consistently either.
WTF?

My mistake. AccleratedRendering. But still...WTF.

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


_______________________________________________
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




_______________________________________________
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

Reply via email to