Hello Klaus,
I vaguelly remember I had a similar problem in the past. After searching in
stackoverflow, it was suggested to use the OpenJDK version of Java, rather
than the Oracle's one.
I had used version 20.0.1. I still have the .tar file I downloaded back
then, it is named "openjdk-20.0.1_maco
Also, in the screenshot you attached, it looks like the arguments
"signing-keystore" and "keystore" expect a different value.
The "keystore" looks like it should be the "android_upload.keystore" you
created and used to sign the app in LiveCode. I am not sure what is the
"signing-keystore" - were y
Hi Panos,
> Am 28.08.2024 um 09:17 schrieb panagiotis merakos via use-livecode
> :
>
> Also, in the screenshot you attached, it looks like the arguments
> "signing-keystore" and "keystore" expect a different value.
>
> The "keystore" looks like it should be the "android_upload.keystore" you
> c
("936,474" is within "777,50,1424,1") -> true
("936,474" is within "777,50,1424,10") -> false
LC 9.6.9 on Mac OSX 10.15
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
Klaus:
> I really need your help, please, deadline is saturday! :-/
It has been almost a couple of years since last Android project;
my current laptop is not set up for it yet. But ...
Panos:
> I vaguely remember I had a similar problem in the past. After
> searching in stackoverflow, it was s
Hi Panos,
I had created a new keystore and PEM file with the shell commands that Gooogle
support supplied.
Still no joy...
% java -jar pepk.jar --keystore=android_upload2.jks --alias=upload
--output=output.zip --rsa-aes-encryption
--encrypti
Hello Klaus,
Hmm this looks like a different error. I also noticed that the new keystore
you created has extension ".jks" and not ".keystore".
Could you try with your old .keystore and .pem file, i.e. something like
this:
java -jar pepk.jar --keystore=android_upload.keystore --alias=sehenkey
--o
Hi Panos,
still no joy...
...
java -jar pepk.jar --keystore=android_upload.keystore --alias=sehenkey
--output=output.zip --rsa-aes-encryption
--encryption-key-path=upload_certificate.pem
Enter password for key 'sehenkey':
Error: Unable to export or encrypt the private key
java.security.spec.Inv
Looks like ~32k is the max value allowed for a coordinate value.
Brian Milby
br...@milby7.com
> On Aug 28, 2024, at 4:22 AM, jbv via use-livecode
> wrote:
>
> ("936,474" is within "777,50,1424,1") -> true
>
> ("936,474" is within "777,50,1424,10") -> false
>
> LC 9.6.9 on Mac OSX 10
Easy enough to test.
put ("936,474" is within "777,50,1424,32767”) —> true
put ("936,474" is within "777,50,1424,32768”) —> false
Bob S
> On Aug 28, 2024, at 5:17 AM, Brian Milby via use-livecode
> wrote:
>
> Looks like ~32k is the max value allowed for a coordinate value.
>
> Brian Milby
Exactly (that is essentially what I did)
The actual full rect is:
(-32768,-32768,32767,32767)
Brian Milby
br...@milby7.com
> On Aug 28, 2024, at 11:19 AM, Bob Sneidar via use-livecode
> wrote:
>
> Easy enough to test.
>
> put ("936,474" is within "777,50,1424,32767”) —> true
> put ("936,474
> Am 28.08.2024 um 19:07 schrieb Brian Milby via use-livecode
> :
>
> Exactly (that is essentially what I did)
>
> The actual full rect is:
> (-32768,-32768,32767,32767)
should suffice for a simple addressbook app. :-)
> Brian Milby
> br...@milby7.com
>
>> On Aug 28, 2024, at 11:19 AM, Bob
Le 2024-08-28 13:52, Klaus major-k via use-livecode a écrit :
should suffice for a simple addressbook app. :-)
yep, but not for processing any kind of raw data...
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to
put "777,50,1424,1" into tCoords
put item 1 of tCoords > -32768 AND \
item 2 of tCoords > -32768 AND \
item 3 of tCoords < 32767 AND \
item 4 of tCoords < 32767 AND \
"936,474" is within tCoords --> true
put "777,50,1424,10" into tCoords
put item 1 of tCoords > -32768 AND \
item 2 of tCoor
14 matches
Mail list logo
