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 a

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

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 t

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 t

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

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

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 comp

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 a

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

Re: acceleratedRendering

I don't know if it would work on a iOS 12, but we has an issue with a complex dynamic "draw" on screen.. So we turned of acceleratedRendering to false temporarily Then set to back when the drawing was finish on createWordPuzzle if (the acceleratedRendering of this stack is true ) then

Re: acceleratedRendering

Next week will be fine __ Brahmanathaswami On 8/2/18, 1:23 PM, "use-livecode on behalf of Monte Goulding via use-livecode" wrote: Given it’s Friday and these patches have yet to be reviewed I very much doubt we will be releasing an RC 2 with them in this week. We do have a service pro

Re: acceleratedRendering

> @team-- would it possible to send a new build out this week? Even it has > only this patch > > It is the one thing in Android that is blocking. Everything else you have > accomplished on 9.0.1 is fantastic, and I really *need* get an Android > version that works one on Google Play asap. So

Re: acceleratedRendering

pdate out the door quickly as users are already complaining about iOS 12 compatibility. You've given me some insight into the possible problem so I can try to work out a proper bug report formula. --Andrew Bell From: Sannyasin Brahmanathaswami To: How to use LiveCode Subject: Re: acc

Re: acceleratedRendering

All, I’ve been messing with this slowdown issue … there is a connection between having acceleratedRendering set to true… and my objects that move set to dynamic. I see the slowdown in the IDE and on the iPad. Using LC 9.0.1 RC1 still. The “catch” is that I haven’t been able to reproduce the s

Re: acceleratedRendering

Aloha Monte You are wonderful! "it groups not redrawing..." Right, it's not "touch". Though from a user perspective, suddenly "my swiping doesn't work..." And thank you for fixing the returnField error also [Bug 18395] ReturninField error on android app) @team-- would it possible to send a n

Re: acceleratedRendering

Hi Brahma > > I am sure it is a priority with team. Keep fingers crossed. Yes I just patched it https://github.com/livecode/livecode/pull/6620 > FWIW... acceleratedRendering in causing trouble on Android, 9.0.1. RC 1. > > Disables "touch" mess

Re: acceleratedRendering

FWIW... acceleratedRendering in causing trouble on Android, 9.0.1. RC 1. Disables "touch" messages in some contexts... Bug report is in, confirmed. I've struggling for 2 Years with this (!) Now on iOS? Yikes! I am sure it is a priority with team. Keep fingers crossed. BR On 8/1/18, 4:

Re: AcceleratedRendering States When Opening and Closing Stacks

On 9/30/17 12:42 PM, Sannyasin Brahmanathaswami via use-livecode wrote: Our symptom is, (as you know) the objects for stack A still appear on screen, ( only on Android) even if you log for the current top stack and LC engine returns "Stack B" we are seeing the contents of the card for Stack A

Re: AcceleratedRendering States When Opening and Closing Stacks

Well …"exactly" And that is what we want to clarify if stack A is open and contents for its front card are buffered. Now open stack B on top of stack A with Accelerated Rendering on.. Just then… before we close Stack, for n number of milliseconds we have buffered objects for 2 different card

Re: AcceleratedRendering States When Opening and Closing Stacks

I doubt the layermode is an issue here. Layermode is relevant only when the card is open. I'm not where I can review Mark's post about it, but I think acceleratedRendering basically tells the engine to buffer the content of designated controls so they will move smoothly. The layermode tells th

Re: AcceleratedRendering States When Opening and Closing Stacks

It's not set for "everything" only scrolling groups. How can it be drawing too much? if there is only one scrolling group on the card and all other cards, stacks etc are closed or not in view, how does having the layermode set in an unopened stack start to "draw too much" ?? Jonathan Lynch w

Re: AcceleratedRendering States When Opening and Closing Stacks

It seems like having the layermode set to scrolling for everything forces it to draw too much stuff. What happens if you only do one at a time? Mark W would know more. But, I have found one at a time means it only gives extra power where it is needed. Sent from my iPhone > On Sep 29, 2017, at

Re: AcceleratedRendering States When Opening and Closing Stacks

Jonathan: The layermode of the scrolling groups is preset to "scrolling" The question is about the sequence as it relates to visual layer rendering Open Stack A, turn on acceleratedRendering Open Stack B, which also turns on its "own" acceleratedRendering Close Stack A, *after* having open B "o

Re: AcceleratedRendering States When Opening and Closing Stacks

Hi Swami, I turn accelerated rendering on and off depending on which group the user opens up. Are you setting the layermode of each group as you go? Sent from my iPhone > On Sep 29, 2017, at 1:41 PM, Sannyasin Brahmanathaswami via use-livecode > wrote: > > We continue struggle with our app

Re: acceleratedRendering scope

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

Re: acceleratedRendering scope

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

Re: acceleratedRendering scope

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

Re: acceleratedRendering scope

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

Re: acceleratedRendering scope

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

Re: acceleratedRendering scope

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

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

Hi Scott and Jacque, Thanks for the help… I've been exploring colorOverlay… looks like I can make it work. be well, randy - On Jul 22, 2012, at 12:14 AM, Scott Rossi wrote: > The first question to Randy would be, why do you want to change the image to > black? What's the end effect you'r

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

The first question to Randy would be, why do you want to change the image to black? What's the end effect you're going for? Would something like the coloroverlay graphic effect be a workable option? Regards, Scott Rossi Creative Director Tactile Media, UX Design On Jul 21, 2012, at 10:06 PM

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

Those are them. Regards, Scott Rossi Creative Director Tactile Media, UX Design On Jul 21, 2012, at 10:01 PM, "J. Landman Gay" wrote: > On 7/21/12 11:34 PM, Scott Rossi wrote: >> >> I don't have LiveCode in front of me but I'm pretty sure the docs >> list several of the ink limitations of acc

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

On 7/21/12 11:06 PM, Randy Hengst wrote: The Imaging Blends do work with accelerated rendering set to true… But, none of them will turn the image black… or dark gray… these blends are influenced by the background color. Is it to be expected that acceleratedRendering will disable the Structural

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

On 7/21/12 11:34 PM, Scott Rossi wrote: I don't have LiveCode in front of me but I'm pretty sure the docs list several of the ink limitations of acceleratedRendering there. I just found it in the 5.02 release notes: Accelerated rendering comes with some restrictions: • Bitmap effects which us

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

Randy: I don't have LiveCode in front of me but I'm pretty sure the docs list several of the ink limitations of acceleratedRendering there. Regards, Scott Rossi Creative Director Tactile Media, UX Design On Jul 21, 2012, at 9:06 PM, Randy Hengst wrote: > Hi Jacque, > > Thanks for the scoo

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

Hi Jacque, Thanks for the scoop. That's good to know… To be honest, since they are still listed under the blend options, I didn't think about them being discontinued. As I mentioned, "clear" still turns the image black (like I want) in my original app … I didn't notice the problem until I added

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

On 7/21/12 5:37 PM, Randy Hengst wrote: I've set the INK on the draggable images to "clear" when the image is first shown to the user… with accelerated rendering set to false, the image is black…. with accelerated rendering set to true, the image seems to be stuck in its original color... In ot

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

Hi Klaus and All, I'm just now trying to get my head around accelerated rendering. I don't have access to Windows, so can't comment specifically on what Klaus discovered. However, I can confirm a problem with INK and accelerated rendering on LC5.5.1 when running the app on iOS simulator or dev

Re: acceleratedRendering is my friend

Chip and Tom, thanks for clarifying. Matthias Am 28.06.2012 um 22:11 schrieb Chipp Walters: > Just wanted to share a couple other key points Tom and I discussed after > lunch today: > > The object of the control you are setting the dynamic or scrolling property > of MUST be a toplevel control.

Re: acceleratedRendering is my friend

Chris, Yes, that bug is in the using of visual effects which i believe they are aware of with VE, there is also an issue with responsiveness using them. -- Tom McGrath III http://lazyriver.on-rev.com 3mcgr...@comcast.net On Jun 28, 2012, at 4:30 PM, Chris Sheffield wrote: > I just checked this

Re: acceleratedRendering is my friend

I just checked this in LC 5.5.1 to make sure, and there is still a bug that exists where the screen will flash when toggling acceleratedRendering if you're moving from card to card using a visual effect. A ticket has already been submitted. The way around it is to set the property in a handler,

Re: acceleratedRendering is my friend

Just wanted to share a couple other key points Tom and I discussed after lunch today: The object of the control you are setting the dynamic or scrolling property of MUST be a toplevel control. IOW, the *parent* of the control MUST be the card. So, you can't accelerate objects within groups, but ra

Re: acceleratedRendering is my friend

Matthias, It was my understanding that for scrolling you would create the scroller at the preOpenCard after you set the acceleratedRendering and the layerMode: on preOpenCard set the acceleratedRendering of this stack to true set the layerMode of group "OptionGroups" of card "Settings1" t

Re: acceleratedRendering is my friend

Hi Tom, thanks for sharing this with us. >>> . Immediately before moving an object turn on dynamic or when scrolling a >>> group turn on scrolling >>> once moving the scroll or object has already been cached and drawn so these >>> are no longer necessary. No need to turn these things on and lea

Re: acceleratedRendering is my friend

>From what Mark said the preopencard is the place to do it and I have not seen >any flashing in 5.5.1 -- Tom McGrath III http://lazyriver.on-rev.com 3mcgr...@comcast.net On Jun 27, 2012, at 2:27 PM, Chris Sheffield wrote: > Tom, > > Thanks for the info. Very useful. > > I haven't actually tri

Re: acceleratedRendering is my friend

Tom, Thanks for the info. Very useful. I haven't actually tried any of this yet, but is there still a problem where the screen flashes when toggling acceleratedRendering on/off in preOpenCard and closeCard? I was seeing this a couple months back, so I'm curious if that still exists. I haven't

Re: acceleratedRendering is my friend

On Wed, Jun 27, 2012 at 11:57 AM, Thomas McGrath III wrote: > After sitting with Mark W. for an hour over lunch yesterday I was able to > both understand the role of acceleratedRendering and the best usage of it. > It turns out that the order of when these commands are used is of utmost > importan

Re: acceleratedrendering = true and ink = NOOP don't cooperate :-/

Hi all, Am 03.05.2012 um 20:23 schrieb Klaus on-rev: > Hi freinds > > I just found an evil bug on the Mac :-/ > LiveCode 5.02 > > When you "set the acceleratedrendering of this stack to true" > all objects with their INK set to NOOP will become visible again. > > This does not happen on Window