Re: slow slower slowest scroll on Android

[Sphere via use-livecode]

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 , 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 what
architecture it is, like also commonly is used with serial nr's from
tv's for example.

I will create a feature request.

Thanks very much.

Best regards,

Jerry

Mark Waddingham via use-livecode schreef op 2019-05-30 18:09:

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 used for which type of APK.


LiveCode only supports Android 4.x and above, and all devices which 
run
4.x have at the very least an ARMv7 processor - so there isn't any 
need
for a ARMv6 device build anymore (hence why it has been removed in 
9.5).



Is it possible as feature, that there can be a checkbox added, so you
can choose to have separate builds instead of one multiple build when
more then 1 build is chosen?


That would be quite a useful thing to have - perhaps a check-box which
'builds separate APKs' on the standalone settings pane. It could also
do something to derive a new versionCode (they all have to be 
different).

e.g.

APK-versionCode = S/B-specified-versionCode * 10 + arch-index

   arch-index = 0 (ARMv7), 1 (ARM64), 2 (x86), 3 (x86-64)

That would save having to specify (by hand) several different 
versionCodes

for each build.

Could you file an enhancement request for such an option, and we can 
see what

we can do.

Warmest Regards,

Mark.


___
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: slow slower slowest scroll on Android

[Sphere via use-livecode]

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 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
"dgBackground" of your
DataGrid group. From memory, I believe that is a graphic, which sits
behind everything
else (within the Datagrid). At the very least, you should be able to
get the border
back, if not the glow (as it would be clipped away by the datagrid's
top-level group).

Warmest Regards,

Mark.


___
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: slow slower slowest scroll on Android

[Sphere via use-livecode]

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 what architecture 
it is, like also commonly is used with serial nr's from tv's for 
example.


I will create a feature request.

Thanks very much.

Best regards,

Jerry

Mark Waddingham via use-livecode schreef op 2019-05-30 18:09:

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 used for which type of APK.


LiveCode only supports Android 4.x and above, and all devices which run
4.x have at the very least an ARMv7 processor - so there isn't any need
for a ARMv6 device build anymore (hence why it has been removed in 
9.5).



Is it possible as feature, that there can be a checkbox added, so you
can choose to have separate builds instead of one multiple build when
more then 1 build is chosen?


That would be quite a useful thing to have - perhaps a check-box which
'builds separate APKs' on the standalone settings pane. It could also
do something to derive a new versionCode (they all have to be 
different).

e.g.

APK-versionCode = S/B-specified-versionCode * 10 + arch-index

   arch-index = 0 (ARMv7), 1 (ARM64), 2 (x86), 3 (x86-64)

That would save having to specify (by hand) several different 
versionCodes

for each build.

Could you file an enhancement request for such an option, and we can 
see what

we can do.

Warmest Regards,

Mark.


___
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: slow slower slowest scroll on Android

[Mark Waddingham via use-livecode]

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 
"dgBackground" of your
DataGrid group. From memory, I believe that is a graphic, which sits 
behind everything
else (within the Datagrid). At the very least, you should be able to get 
the border
back, if not the glow (as it would be clipped away by the datagrid's 
top-level group).


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: slow slower slowest scroll on Android

[Mark Waddingham via use-livecode]

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 used for which type of APK.


LiveCode only supports Android 4.x and above, and all devices which run
4.x have at the very least an ARMv7 processor - so there isn't any need
for a ARMv6 device build anymore (hence why it has been removed in 9.5).


Is it possible as feature, that there can be a checkbox added, so you
can choose to have separate builds instead of one multiple build when
more then 1 build is chosen?


That would be quite a useful thing to have - perhaps a check-box which
'builds separate APKs' on the standalone settings pane. It could also
do something to derive a new versionCode (they all have to be 
different).

e.g.

APK-versionCode = S/B-specified-versionCode * 10 + arch-index

   arch-index = 0 (ARMv7), 1 (ARM64), 2 (x86), 3 (x86-64)

That would save having to specify (by hand) several different 
versionCodes

for each build.

Could you file an enhancement request for such an option, and we can see 
what

we can do.

Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: slow slower slowest scroll on Android

[Sphere via use-livecode]

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 dependencies.


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 used for which type of APK.


Also when Google signing is used there is an option to have dependencies 
build, but probably that is only useful for users of Android Studio.So 
then only the parts being needed are installed, as far as i understood 
it.



Thanks Monte for confirming it, that it will push the build upon the 
target architecture.


Is it possible as feature, that there can be a checkbox added, so you 
can choose to have separate builds instead of one multiple build when 
more then 1 build is chosen?



Indeed that would be a nice addition you proposed.


Regards,

Jerry

Monte Goulding via use-livecode schreef op 2019-05-29 23:27:
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 what you
have selected in the standalone settings. This means you can leave
armv7 and arm64 selected for release builds and the Test button will
deploy x86 if you are targeting an x86 emulator.

Note I just created this enhancement request to add the target
architecture in parenthesis after the target name in the menu.
https://quality.livecode.com/show_bug.cgi?id=22114


Cheers

Monte
___
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: slow slower slowest scroll on Android

[Monte Goulding via use-livecode]

> 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 what you have selected in 
the standalone settings. This means you can leave armv7 and arm64 selected for 
release builds and the Test button will deploy x86 if you are targeting an x86 
emulator.

Note I just created this enhancement request to add the target architecture in 
parenthesis after the target name in the menu. 
https://quality.livecode.com/show_bug.cgi?id=22114 


Cheers

Monte
___
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: slow slower slowest scroll on Android

[Ralph DiMola via use-livecode]

Jerry,

First of all... The armv7 will work on all architectures. The Intels have an
arm emulator that in my tests are about 7-10 times slower than a native
Intel build. Arm 64 will only work on 64 bit arm architectures. Intel will
work on all Intel architectures and Intel 64 will work on only 64 bit
Intels. (I think a have this straight)

Testing: If you push all 4 types to a test device the test device will use
the best architecture. This will make the apk huge and some devices have a
apk size limit. The build/install also takes longer. When testing use only
one architecture and pick the best for your test device.

PlayStore distribution: If you build 1 apk for all 4 architectures the apk
will be huge and you may exceed the max apk limit for some devices. The best
way is to build 4 apks one for each architecture. Up the version code by at
least 1 for each build. Upload and release all 4 apks to production on the
PlayStore. When a user installs your app from the PlayStore the best apk for
their device will be installed. This makes for a faster/less data install
for users.

The restrictions for multiple apks on the PlayStore is 1) the version codes
must be different 2) the apks must not target duplicate architectures. This
is why you can have 4 apks in production at the same time.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of JJS 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 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 Monte/Brian.

So in standalone i only now had the ARM64 selected and then build it in
dev/test mode.

(What will it push to the phone if all 4 options are selected? does it check
what is connected?)


This looks very good. Now i want to test further with the grid 
containing images and text fields, see how that performs.


Regards,

Jerry


Op 29-5-2019 om 21:24 schreef JJS via use-livecode:
> 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, then use a 
>> separate object for the effect behind the DG so you can get the 
>> performance boost from accelerated rendering.
>>
>> Thanks,
>> Brian
>> On May 29, 2019, 2:28 AM -0700, Sphere via use-livecode 
>> , wrote:
>>> 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 around it.
>>> Ok will test tonight.
>>>
>>> Thanks!
>>>
>>> Monte Goulding via use-livecode schreef op 2019-05-28 23:23:
>>>>> 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 layerMode group in the datagroup is about 3 levels in with
>>>> its parents being container. As mentioned on other posts you need to
>>>> ensure the datagrid is unadorned (no border etc). Also if you have it
>>>> placed inside a group then that group must also be set to container
>>>> layerMode and be unadorned.
>>>>
>>>> Cheers
>>>>
>>>> Monte
>>>> ___
>>>> 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.runre

Re: slow slower slowest scroll on Android

[JJS via use-livecode]

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 Monte/Brian.

So in standalone i only now had the ARM64 selected and then build it in 
dev/test mode.


(What will it push to the phone if all 4 options are selected? does it 
check what is connected?)



This looks very good. Now i want to test further with the grid 
containing images and text fields, see how that performs.



Regards,

Jerry


Op 29-5-2019 om 21:24 schreef JJS via use-livecode:

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, then use a 
separate object for the effect behind the DG so you can get the 
performance boost from accelerated rendering.


Thanks,
Brian
On May 29, 2019, 2:28 AM -0700, Sphere via use-livecode 
, wrote:

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 around it.
Ok will test tonight.

Thanks!

Monte Goulding via use-livecode schreef op 2019-05-28 23:23:

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 layerMode group in the datagroup is about 3 levels in with
its parents being container. As mentioned on other posts you need to
ensure the datagrid is unadorned (no border etc). Also if you have it
placed inside a group then that group must also be set to container
layerMode and be unadorned.

Cheers

Monte
___
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


___
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: slow slower slowest scroll on Android

[JJS via use-livecode]

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, then use a separate object 
for the effect behind the DG so you can get the performance boost from 
accelerated rendering.

Thanks,
Brian
On May 29, 2019, 2:28 AM -0700, Sphere via use-livecode 
, wrote:

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 around it.
Ok will test tonight.

Thanks!

Monte Goulding via use-livecode schreef op 2019-05-28 23:23:

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 layerMode group in the datagroup is about 3 levels in with
its parents being container. As mentioned on other posts you need to
ensure the datagrid is unadorned (no border etc). Also if you have it
placed inside a group then that group must also be set to container
layerMode and be unadorned.

Cheers

Monte
___
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: slow slower slowest scroll on Android

[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, then use a separate object 
for the effect behind the DG so you can get the performance boost from 
accelerated rendering.

Thanks,
Brian
On May 29, 2019, 2:28 AM -0700, Sphere via use-livecode 
, wrote:
> 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 around it.
> Ok will test tonight.
>
> Thanks!
>
> Monte Goulding via use-livecode schreef op 2019-05-28 23:23:
> > > 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 layerMode group in the datagroup is about 3 levels in with
> > its parents being container. As mentioned on other posts you need to
> > ensure the datagrid is unadorned (no border etc). Also if you have it
> > placed inside a group then that group must also be set to container
> > layerMode and be unadorned.
> >
> > Cheers
> >
> > Monte
> > ___
> > 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: slow slower slowest scroll on Android

[Sphere via use-livecode]

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 around it.
Ok will test tonight.

Thanks!

Monte Goulding via use-livecode schreef op 2019-05-28 23:23:
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 layerMode group in the datagroup is about 3 levels in with
its parents being container. As mentioned on other posts you need to
ensure the datagrid is unadorned (no border etc). Also if you have it
placed inside a group then that group must also be set to container
layerMode and be unadorned.

Cheers

Monte
___
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: slow slower slowest scroll on Android

[Monte Goulding via use-livecode]

> 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 
layerMode group in the datagroup is about 3 levels in with its parents being 
container. As mentioned on other posts you need to ensure the datagrid is 
unadorned (no border etc). Also if you have it placed inside a group then that 
group must also be set to container layerMode and be unadorned.

Cheers

Monte
___
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: slow slower slowest scroll on Android

[Tom Glod via use-livecode]

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 dictionary app I literally cringe
at the text rendering and "scrolling".

Can't wait for something that feels like its modern or at least 2010 ish.

rant over.

On Tue, May 28, 2019 at 3:49 PM JJS via use-livecode <
use-livecode@lists.runrev.com> wrote:

> 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. On another stack i'm working on i have 2
> native fields of which one is scrolling and the other not, so i have to
> check what is going on there.
>
> But for this one, the field is over the whole card almost with
> informative text. If the native field is not working well then i will
> change it to also an answer pop-up instead of a card.
>
> Also when swiping up when lifting up your finger it sees it as a
> mouseUp. Have to see what i can do about that.
>
>
> Regards,
>
> Jerry
>
>
> Op 28-5-2019 om 20:46 schreef Brian Milby via use-livecode:
> > 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 28, 2019, 11:13 AM -0700, JJS via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
> >> 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 influence)
> >>
> >> And the influence is minor, still it is stuttering, and even the simple
> >> field is not great.
> >>
> >> It's no comparison with an Answer pop-up.
> >>
> >> Will try a 64bit next, but then again even on a quad core it should
> >> scroll smoother.
> >>
> >>
> >> Regards,
> >>
> >> Jerry
> >>
> >> Op 28-5-2019 om 18:35 schreef J. Landman Gay via use-livecode:
> >>> 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 10:58:07 AM JJS via use-livecode
> >>>  wrote:
> >>>
>  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 scrolling is with a lot of text in an answer pop-up, this
> scrolls
>  how it should be.
> 
>  -Average scrolling is a text field with a lot of text
> 
>  -and very slow stuttering is a DG2 with just lines of text in it
> (about
>  6000 lines of text with a single word)
> 
> 
>  I still have to test another DG2 with images and text in it, but i
> don't
>  expect any better.
> 
> 
>  It should scroll like apps as Instagram and Facebook etcetera.
> 
>  Any experiences of others?
> 
> 
>  Regards,
> 
>  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
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > 

Re: slow slower slowest scroll on Android

[JJS via use-livecode]

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. On another stack i'm working on i have 2 
native fields of which one is scrolling and the other not, so i have to 
check what is going on there.


But for this one, the field is over the whole card almost with 
informative text. If the native field is not working well then i will 
change it to also an answer pop-up instead of a card.


Also when swiping up when lifting up your finger it sees it as a 
mouseUp. Have to see what i can do about that.



Regards,

Jerry


Op 28-5-2019 om 20:46 schreef Brian Milby via use-livecode:

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 28, 2019, 11:13 AM -0700, JJS via use-livecode 
, wrote:

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 influence)

And the influence is minor, still it is stuttering, and even the simple
field is not great.

It's no comparison with an Answer pop-up.

Will try a 64bit next, but then again even on a quad core it should
scroll smoother.


Regards,

Jerry

Op 28-5-2019 om 18:35 schreef J. Landman Gay via use-livecode:

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 10:58:07 AM JJS via use-livecode
 wrote:


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 scrolling is with a lot of text in an answer pop-up, this scrolls
how it should be.

-Average scrolling is a text field with a lot of text

-and very slow stuttering is a DG2 with just lines of text in it (about
6000 lines of text with a single word)


I still have to test another DG2 with images and text in it, but i don't
expect any better.


It should scroll like apps as Instagram and Facebook etcetera.

Any experiences of others?


Regards,

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

___
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: slow slower slowest scroll on Android

[Brian Milby via use-livecode]

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 28, 2019, 11:13 AM -0700, JJS via use-livecode 
, wrote:
> 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 influence)
>
> And the influence is minor, still it is stuttering, and even the simple
> field is not great.
>
> It's no comparison with an Answer pop-up.
>
> Will try a 64bit next, but then again even on a quad core it should
> scroll smoother.
>
>
> Regards,
>
> Jerry
>
> Op 28-5-2019 om 18:35 schreef J. Landman Gay via use-livecode:
> > 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 10:58:07 AM JJS via use-livecode
> >  wrote:
> >
> > > 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 scrolling is with a lot of text in an answer pop-up, this scrolls
> > > how it should be.
> > >
> > > -Average scrolling is a text field with a lot of text
> > >
> > > -and very slow stuttering is a DG2 with just lines of text in it (about
> > > 6000 lines of text with a single word)
> > >
> > >
> > > I still have to test another DG2 with images and text in it, but i don't
> > > expect any better.
> > >
> > >
> > > It should scroll like apps as Instagram and Facebook etcetera.
> > >
> > > Any experiences of others?
> > >
> > >
> > > Regards,
> > >
> > > 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
___
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: slow slower slowest scroll on Android

[JJS via use-livecode]

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 influence)


And the influence is minor, still it is stuttering, and even the simple 
field is not great.


It's no comparison with an Answer pop-up.

Will try a 64bit next, but then again even on a quad core it should 
scroll smoother.



Regards,

Jerry

Op 28-5-2019 om 18:35 schreef J. Landman Gay via use-livecode:
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 10:58:07 AM JJS via use-livecode 
 wrote:



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 scrolling is with a lot of text in an answer pop-up, this scrolls
how it should be.

-Average scrolling is a text field with a lot of text

-and very slow stuttering is a DG2 with just lines of text in it (about
6000 lines of text with a single word)


I still have to test another DG2 with images and text in it, but i don't
expect any better.


It should scroll like apps as Instagram and Facebook etcetera.

Any experiences of others?


Regards,

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: slow slower slowest scroll on Android

[J. Landman Gay via use-livecode]

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 10:58:07 AM JJS via use-livecode 
 wrote:



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 scrolling is with a lot of text in an answer pop-up, this scrolls
how it should be.

-Average scrolling is a text field with a lot of text

-and very slow stuttering is a DG2 with just lines of text in it (about
6000 lines of text with a single word)


I still have to test another DG2 with images and text in it, but i don't
expect any better.


It should scroll like apps as Instagram and Facebook etcetera.

Any experiences of others?


Regards,

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

RE: slow slower slowest scroll on Android

[Ralph DiMola via use-livecode]

Did you try an arm64 build with 9.5.0?

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of JJS via use-livecode
Sent: Tuesday, May 28, 2019 11:56 AM
To: How 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 know how it is with others their experiences but...

-Best scrolling is with a lot of text in an answer pop-up, this scrolls how
it should be.

-Average scrolling is a text field with a lot of text

-and very slow stuttering is a DG2 with just lines of text in it (about
6000 lines of text with a single word)


I still have to test another DG2 with images and text in it, but i don't 
expect any better.


It should scroll like apps as Instagram and Facebook etcetera.

Any experiences of others?


Regards,

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

slow slower slowest scroll on Android

[JJS via use-livecode]

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 scrolling is with a lot of text in an answer pop-up, this scrolls 
how it should be.


-Average scrolling is a text field with a lot of text

-and very slow stuttering is a DG2 with just lines of text in it (about 
6000 lines of text with a single word)



I still have to test another DG2 with images and text in it, but i don't 
expect any better.



It should scroll like apps as Instagram and Facebook etcetera.

Any experiences of others?


Regards,

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