acceleratedRendering bugs

[JJS]

BUG 10881 seems solved now for the accelerated rendering, it solves the 
pushed up screen of a stack after the keyboard popped up

Thanks Monte!

Very Nice!

Op 12-3-2019 om 14:00 schreef Sphere via use-livecode:
> Thanks for your reply Randy.
> Nice app you made.
>
> I noticed it is sensitve and that the DG2 group with images and text 
> got even slower.
> So i have to play some more to get it more smoother as it looked more 
> cloggy when scrolling.
> i can try the max and see if it will have some effect. I also tried it 
> on BlueStacks after i saw the hint from Richmond.
> That should be very fast, as we have to wait on 9.1 before we can use 
> the fast x86 emulator.
> But even in BlueStacks the DG is slow and cloggy.
>
> Randy Hengst via use-livecode schreef op 2019-03-12 11:38:
>> My work is only with  iOS. So, no comments about Android…
>>
>> But, I found while working a recent iPad app (with many moving
>> controls) that I needed to adjust the layerMode to dynamic and back to
>> static after the move.
>>
>> I also increased the compositorCacheLimit as you noted… only I went up
>> to 256*1024*1024.
>> I made this adjustment in the startUp handler.
>>
>> I even needed to up the compositorCacheLimit while working in the IDE.
>> I made that adjustment in the message box.
>>
>> I didn’t make any changes relative to compositorTileSize or 
>> compositorType.
>>
>> The app I was developing when I first started making these adjustments
>> is free (if that will help understand my context) ….
>> here is the Apple App Preview page:
>> https://itunes.apple.com/us/app/begotten/id1431461736?mt=8
>>
>>
>> be well,
>> randy
>> www.classroomFocusedSoftware.com
>>
>>
>>> On Mar 11, 2019, at 4:13 PM, JJS via use-livecode 
>>> <use-livecode at lists.runrev.com> wrote:
>>>
>>> i was playing a bit with the separate command you can use instead of 
>>> acceleratedrendering (on Android mobile)
>>>
>>> compositorTileSize,layerMode,compositorType,compositorCacheLimit
>>>
>>> and noticed that setting compositorType to opengl for android causes 
>>> the black out screen
>>>
>>> i'm not sure yet about compositorTileSize what it does on speed
>>>
>>> the compositorCacheLimit needs to be big like 64*1024*1024 for 64MB 
>>> according calculation in the dictionary, if you set it small it gets 
>>> slow updated
>>>
>>> now i'm not sure if i need the separate commands to be set empty in 
>>> the closecard (to prevent upshifting on other cards when using 
>>> keyboard) or that setting the acceleratedrendering to false would be 
>>> enough.
>>>
>>> till now i set the accelerated rendering on and off depending if i 
>>> need keyboard on the card
>>>
>>>
>>> anyone else have experience with these commands?
>>>
>>>
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode