Hurray! That worked:
Version code 15
Native platforms arm64-v8a, armeabi-v7a.
74.9 MB
Version code 9
Native platforms x86_64
64.0 MB
Version code 8
Native platforms x86
63.7 MB
-- No "overshowed" ERROR
-- One warning about extra code in the bui
All is fine on both my Pixel and Huawei MediaPad m5.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 13, 2019 3:23:31 PM Matthias Rebbe via use-livecode
wrote:
Hi,
yesterday i´ve received an email from a user who informed me t
Try making 1 build for armv7 AND arm64
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
Sannyasin Brahmanathaswami via use-livecode
Sent: Thursday, June 13
Aloha Jerry, I think I have done it correctly
1)
I have the four builds in one release
2)
Native platforms -- armeabi-v7a- version code 14
Native platforms -- x86_64 - version code 9
Native platforms -- x86- version code 8
Native platforms -
This works for me on macOS Mojave 10.14.15 using LiveCode 9.0.4. By "works", I
mean it does some things that I think might be close to what you want. I have
a field named "test field" on a card and button to clear that. I hold down keys
while the field does not have the focus. I would guess y
Sony Xperia Z1 (Android 4.4.2):
All is readable as wanted, Impressum starts at top, Disclaimer starts at bottom.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
pref
On my iPad there is something going on to reposition the page. I can scroll
down to see the bottom text but when I let go, it snaps to the top of the
section in a short while.
Thanks,
Brian
On Jun 13, 2019, 4:30 PM -0400, Dar Scott Consulting via use-livecode
, wrote:
> I see those on my old a
Looks OK on an LG v20 7.0. One thing I noticed is that the menu icon does not
appear until you scroll down 3/4 of the way of the first section then is hidden
again if you scroll back up to the top.
Sounds like a cache issue. If a page refresh does not work then have the user
clear their browser
I see those on my old android phone. A popup blocked things for a bit in the
android web browser and in the Chrome browser, it took a bit to clear it.
> On Jun 13, 2019, at 2:21 PM, Matthias Rebbe via use-livecode
> wrote:
>
> Hi,
>
> yesterday i´ve received an email from a user who informe
Hi,
yesterday i´ve received an email from a user who informed me that my website
was not completely visible on his Samsung S7 Edge phone.
Better said, some text at the bottom of some pages (e.g. pages impressum,
disclaimer) was not visible.
I could replicate this even on my iPhone and modified
as far as i've read, Google Play will look for the architecture of the
device where the app will be installed and then pushes the best fit to it.
Just like LC950dp1 now is checking the device before pushing a stack to
test on your phone. Monte confirmed LC does it and you can also quickly
see
Perhaps this would need a delay after the pass. For example, wait until the key
is up and then maybe wait a bit more. This would allow all of the events to
come in before they are flushed. Maybe.
(I think my state-variable method is simpler, but simple is in the eye of the
beholder.)
> On Jun
This thing that confuses me is that the error was for "shadowing". My question
is why does armv7 shadow(ie; target the same device natively) as arm64?
I wonder if there should be only 2 builds 1)armv7 AND arm64 2) Intel AND Intel
64? Theoretically the armv7 and arm64 will both work on a arm64 dev
your version code needs to be higher than the previous one, each time
you upload an update
you could do:
arm-v7a vc1 arm64 vc2 x86 vc3 x86-64 vc4
then next update of your app:
arm-v7a vc5 arm64 vc6 x86 vc7 x86-64 vc8
etcetera
when you manage a
But what about this one, it is an "error," not a "warning
For arm64-v8a
ERROR
1 message for APK 7
Fully shadowed APK
Problem:
This APK will not be served to any users because it is completely shadowed by
one or more APKs with higher version codes.
But the other three
I've run into a bug on Windows (and Linux) with regard to popup menus
over a field using mouseMove or mouseWithin.
https://quality.livecode.com/show_bug.cgi?id=22178
There are related bugs:
https://quality.livecode.com/show_bug.cgi?id=7766
https://quality.livecode.com/show_bug.cgi?id=20695
The
4 separate builds give the same optimize warning which you can ignore.
There is a feature request done to have a swith in the standalone
settings, so one can choose to have one big build or 4 separate builds
(or to the nr of set architectures)
The playstore will push the correct build to the
17 matches
Mail list logo
