Hm,
just a shot in the dark, did you enable the Development mode on the tablets?
> Am 12.10.2023 um 15:35 schrieb Klaus major-k via use-livecode
> :
>
> Hi friends,
>
> I am trying to install my app on the tablets of my bandmembers
> and succeeded on all but one!?
>
> Info:
> Samsung
> Am 12.10.2023 um 15:43 schrieb matthias rebbe via use-livecode
> :
>
> Hm,
> just a shot in the dark, did you enable the Development mode on the tablets?
sure!
A propos dark:
At midnight on a graveyard I tapped SEVEN times on the buildnumber,
that should have done the trick, right! :-D
Hi friends,
I am trying to install my app on the tablets of my bandmembers
and succeeded on all but one!?
Info:
Samsung Galaxy Tab S
Android 6.0.1, API 23
After installation from LC (Test) I tap on the icon and get the alert:
-> Leadsheeter stopped (angehalten)
immediately, no more info.
I
I know that HTML5 export is not quite ready yet - but I’m a patient man :)
I would like to know how it works / will work - particularly with regard to
the size of the exports.
With the old JavaScript export you had a separation between the engine and
stacks such that you could cache the engine
Hi Bob,
> Am 12.10.2023 um 17:36 schrieb Bob Sneidar via use-livecode
> :
>
> Hi all.
>
> I have a standalone that uses a splash stack, which upon launch displays a
> startup graphic, then hides itself and opens the mainstack of my project. On
> MacOS when I "quit" the entire application
Hi all.
I have a standalone that uses a splash stack, which upon launch displays a
startup graphic, then hides itself and opens the mainstack of my project. On
MacOS when I "quit" the entire application quits. On Windows however the splash
stack (which is the stack the standalone is built
Heather,
Do you think Apple will address this issue in an update to Sonoma?
Rebuilding all my applications will be difficult.
Thank you,
Bill Vlahos
> On Oct 3, 2023, at 6:56 AM, Heather Laine via use-livecode
> wrote:
>
> Hi Matthias,
>
> I think ANY menu will cause a crash. |f your app
David Bovill wrote:
> With the old JavaScript export you had a separation between the engine
> and stacks such that you could cache the engine part in the browser to
> speed up the loading of the much smaller stacks. Is that the case (or
> it is intended to be the case in the future) with the wasm
Thanks I'll give that a try. I think I am already quitting the splash stack,
because my MacOS works properly, but the second part I never knew about.
Unfortunately my Apple laptop is in the shop so I won't be able to test until
Monday.
Bob S
-Original Message-
From: use-livecode On
ambassa...@fourthworld.com wrote:
"JS is the only interactive language included in browsers. The best time to
learn it was yesterday. The second best time is today."
+1
My today was about 5 years ago. JS has been an asset to my workflow ever
since. Being able get JS callbacks and invoke JS from
Hi Richard specifically I need to know if I create an web page with
multiple HTML5 export embeds whether the Livecode wasm approach forces the
engine to be exported multiple times.
On Thu, 12 Oct 2023 at 17:09, ambassador--- via use-livecode <
use-livecode@lists.runrev.com> wrote:
> David
What minimum Android version is set in Standalone Settings? Does it include
Android 6?
On 10/12/23 8:35 AM, Klaus major-k via use-livecode wrote:
Hi friends,
I am trying to install my app on the tablets of my bandmembers
and succeeded on all but one!?
Info:
Samsung Galaxy Tab S
Android
12 matches
Mail list logo