This line: "Guess i did investigate good enough on the ARM versions."
should be: "Guess i did NOT investigate good enough on the ARM
versions." forgot the NOT
request made: https://quality.livecode.com/show_bug.cgi?id=22118
Sphere via use-livecode schreef op 2019-05-30 19:09:
Thank you Mark
Thanks,
i will go fiddling around to see if it works and else no glow :)
Regards,
Jerry
Mark Waddingham via use-livecode schreef op 2019-05-30 18:13:
On 2019-05-29 23:10, JJS via use-livecode wrote:
Wow, what a difference does it make.
*Phew*
Turned off the nice border glow around the
Thank you Mark , that makes it clear.
Guess i did investigate good enough on the ARM versions.
The arch index is a good idea, somtehing similair is also what i saw
inthe Google explanation on multiple APK's to have a version nr where
the position of the nr identifies what version and for
On 2019-05-29 23:10, JJS via use-livecode wrote:
Wow, what a difference does it make.
*Phew*
Turned off the nice border glow around the grid, turned border off and
set it to zero (the latter won't make difference i guess.)
You could experiment by fiddling with the properties of control
On 2019-05-30 19:54, Sphere via use-livecode wrote:
Perhaps for the older ARMv6 devices we may need 5 versions, but like
you said Google play will push the best APK option for the device. And
yes every APK needs to have a different/higher Version Code. And keep
in check which Version Code you
Thank you Ralph and Monte,
i've read some things about multiple APK's on Google dev. "Lucky" we
don't need to use the Google signing, it's optional. We can just use the
Java keystore.
There is also mentioned what you say Ralph in respect of the different
cpu and other possible
> On 30 May 2019, at 7:10 am, JJS via use-livecode
> wrote:
>
> What will it push to the phone if all 4 options are selected? does it check
> what is connected?
Yes the deploy library (Test button) uses an adb command to detect the target
device architecture and just builds that no matter
via use-livecode
Sent: Wednesday, May 29, 2019 5:10 PM
To: JJS via use-livecode
Cc: JJS
Subject: Re: slow slower slowest scroll on Android
Wow, what a difference does it make.
I saw that the setting was container again so i let it that way.
Turned off the nice border glow around the grid, turned
Wow, what a difference does it make.
I saw that the setting was container again so i let it that way.
Turned off the nice border glow around the grid, turned border off and
set it to zero (the latter won't make difference i guess.)
This is how it should be. Thanks for pointing me to it
Thanks Brian,
i will do some tests and report back.
Regards,
Jerry
Op 29-5-2019 om 18:08 schreef Brian Milby via use-livecode:
DP2 will fix the missing option in the PI to set container mode, but it can be
done from the message box now.
If you need a static border or shadow behind the DG,
DP2 will fix the missing option in the PI to set container mode, but it can be
done from the message box now.
If you need a static border or shadow behind the DG, then use a separate object
for the effect behind the DG so you can get the performance boost from
accelerated rendering.
Thanks,
Strange is, when i opened the stack in 950dp1 and looked at the setting
to set static, dynamic, scrolling. Container was selected, but when you
click on it you can only choose from the 3 previous mentioned and not
container anymore.
Unadorned (had to translate it first...) so no nice edge
> On 29 May 2019, at 5:49 am, JJS via use-livecode
> wrote:
>
> The DG2's where in container mode, now i've set them in scroller.
>
You should not fiddle with the layerMode of the datagrid. The scripts already
set the correct groups to container and scrolling. The actual scrolling
Hi Jerry. please let us know if the scroll ever looks normal and stops
being "Livecody".
sigh.
Its for this reason why I don't really consider Livecode a legit mobile
development platform. Its THE best for desktop, but on mobile its still got
too many warts. Every time i use the LC
The DG2's where in container mode, now i've set them in scroller.
Made an ARM64 with LC950dp1-Indy, now it is getting faster, still not
great, still stuttering but faster.. The field is a bit faster and the
answer even more faster.
The rows have fixed heights.
I can try with a native field.
For the DG2 benefits, the containing group for the DG needs to be in container
mode. Also, the biggest benefit will be seen with fixed height rows. This is
something that comes with 9.5 DP 1.
For the field, you may see better performance if you make it a native field.
Thanks,
Brian
On May
Hi Jacque and Ralph,
this was a stack build on lc904 Indy and acceleratedrendering is true as
the important issues were fixed.
It was already slow on the previous phone ARMv6 quad core.
Oopsa i forgot to set the mentioned field and DG2's to scrolling (but i
did not know if it had much
Check that acceleratedRendering is true for the stack, and that the group
layermode is "scrolling". Datagrids are a slightly different case, LC 9.5
made some fixes for that.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 28, 2019
to use LiveCode
Cc: JJS
Subject: slow slower slowest scroll on Android
Hi,
i just received a new Android phone with an octa-core phone, so i thought
let's check out my new app...especially scrolling.
Well on my old phone it was dissapointing, but on the new mucho faster phone
even still.
I don't
Hi,
i just received a new Android phone with an octa-core phone, so i
thought let's check out my new app...especially scrolling.
Well on my old phone it was dissapointing, but on the new mucho faster
phone even still.
I don't know how it is with others their experiences but...
-Best
20 matches
Mail list logo
