I am overthinking this.
A group that is visible but layered under another object would do it.
1. Turn on accelerated rendering
2. Scroll the group programmatically from top to bottom as many times as
possible in a quarter second.
3. Adjust the div size based on the number of times it can do the
It looks like we need to use a combination of requestAnimationFrame and
performance.now in JavaScript to test the GPU.
I would rather test the GPU in LC, but I don't know how to do that without
having a visible animation on the screen.
Sent from my iPhone
> On Aug 3, 2017, at 9:05 AM, jonathan
Thanks Roger,
In this case, the issue is more with the map presented in a browser widget,
which is less about LC and more about the embedded chrome framework.
I think that my device is not really a high-end android machine, either.
It looks like max-texture-size might be a decent proxy for meas
I would be more inclined to not say in general "...that Android runs
slower...", but rather "Android runs LiveCode apps slower."
There are plenty of Android apps in the Play store that handle large
graphics VERY well on Android. It may or may not be just how LiveCode
rolls, as an improved experie
Hi Hermann,
That page is a great resource!
Some of their measurements might be a good proxy for GPU power, like the max
viewport size and a couple others.
It would be preferable to fully internalize the system check. I will look
through the page source to see what JS commands they use to measu
> Jonathan wrote:
> It sounds like I need to find a way to detect the processing speed
> of the device.
Did you alread try to use webgl? See the source of
https://browserleaks.com/webgl
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
Thank you, Jacqueline,
It sounds like I need to find a way to detect the processing speed of the
device.
If it is below a certain level, it could adjust the div viewport for the map
proportionally to the processing power.
It could reduce the size of the div, then reexpand it, using a 2d trans
Android devices come with a variety of different specifications. The high
end models will be more capable than low end ones. Depending on
manufacturer and model, the graphics card will vary in capability and
available RAM. Screen resolution also makes a difference. I'm using older
test devices
Hello everyone,
I just put my app on a galaxy tab E as a test.
It is painfully slow, but not just in the LC portion of the app. The map,
delivered through a browser widget, is also slow.
So, I used the regular browser (chrome) at the webglearth website. That was
slow too, although not as bad.
