Re: acceleratedRendering bugs
I just tested a stack on Andorid with lots of input fields where i turned the accelerated off everytime. But this fix now works great. So i can leave it on, Thanks a lot! Op 27-3-2019 om 01:35 schreef J. Landman Gay via use-livecode: I'm sending years worth of gratitude and appreciation. You aren't the only one who was bothered by this bug. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On March 26, 2019 5:11:23 PM Monte Goulding via use-livecode wrote: Aha! This one has vexed me for a while now. I thought I had it previously but the issue turned out to be somewhere completely different to where I was looking! On 27 Mar 2019, at 4:23 am, JJS via use-livecode wrote: 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! ___ 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
Re: acceleratedRendering bugs
I'm sending years worth of gratitude and appreciation. You aren't the only one who was bothered by this bug. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On March 26, 2019 5:11:23 PM Monte Goulding via use-livecode wrote: Aha! This one has vexed me for a while now. I thought I had it previously but the issue turned out to be somewhere completely different to where I was looking! On 27 Mar 2019, at 4:23 am, JJS via use-livecode wrote: 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! ___ 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: acceleratedRendering bugs
Aha! This one has vexed me for a while now. I thought I had it previously but the issue turned out to be somewhere completely different to where I was looking! > On 27 Mar 2019, at 4:23 am, JJS via use-livecode > wrote: > > 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! ___ 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: acceleratedRendering bugs
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 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@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
Re: acceleratedRendering bugs
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 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@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
Re: acceleratedRendering bugs
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 > 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@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: acceleratedRendering bugs
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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: acceleratedRendering bugs
I checked github, nothing there yet, but... it's a DP1, so hoepfully ti will be adressed. Maybe it's not an easy one Op 8-3-2019 om 17:46 schreef Tom Glod via use-livecode: Yeah.. accelerated rendering for dg2 and subgroups was moved to release 9.1 a while back. I'm looking forward to it as well. several things that can work in the mean time is * using lower resolution with scaling quality set to normal * updating images after the grid rows have updated. (this enables scrolling to be faster) * large text fields are slow too. so putting in only enough text to render speeds it up alot I am very curious about the speed increase of the grid after these AR changes have been implemented. On Thu, Mar 7, 2019 at 4:18 PM JJS via use-livecode < use-livecode@lists.runrev.com> wrote: Hi, i saw there are stil 17 bugs open on acceleratedRendering. Is there any sight on when they will be solved? (or at least the most bugging ones) Especially the up shifted screen with the keyboards and the black screens (even short when switching cards) on mobile. And could it be cause for slow scrolling of DG's (with images)? I know there are some tricks, but in most cases i turn it off and on again depending what's on the card and if a keyboard has to be used. Thanks, Jerry ___ 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
Re: acceleratedRendering bugs
Yeah.. accelerated rendering for dg2 and subgroups was moved to release 9.1 a while back. I'm looking forward to it as well. several things that can work in the mean time is * using lower resolution with scaling quality set to normal * updating images after the grid rows have updated. (this enables scrolling to be faster) * large text fields are slow too. so putting in only enough text to render speeds it up alot I am very curious about the speed increase of the grid after these AR changes have been implemented. On Thu, Mar 7, 2019 at 4:18 PM JJS via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi, > > > i saw there are stil 17 bugs open on acceleratedRendering. > > Is there any sight on when they will be solved? (or at least the most > bugging ones) > > Especially the up shifted screen with the keyboards and the black > screens (even short when switching cards) on mobile. > > And could it be cause for slow scrolling of DG's (with images)? > > I know there are some tricks, but in most cases i turn it off and on > again depending what's on the card and if a keyboard has to be used. > > > Thanks, > > Jerry > > > > ___ > 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
acceleratedRendering bugs
Hi, i saw there are stil 17 bugs open on acceleratedRendering. Is there any sight on when they will be solved? (or at least the most bugging ones) Especially the up shifted screen with the keyboards and the black screens (even short when switching cards) on mobile. And could it be cause for slow scrolling of DG's (with images)? I know there are some tricks, but in most cases i turn it off and on again depending what's on the card and if a keyboard has to be used. Thanks, Jerry ___ 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
