The standalone builder got some changes some time ago. So maybe with that
changes the behavior how the builder searches for externals was also reworked.
Anyway, you've got it working again. That's the main thing.
> Am 28.09.2021 um 13:49 schrieb Tiemo via use-livecode
>
Somehow I doubt that the process will be so crude that (e.g. Livecode.com
DNS resolution fails) all standalones built with the Starter Plan would
stop working. I'd imagine that the check for validity would happen for
several days/weeks before an app stopped working. It surely isn't in LC
Ltd's
Hello Matthias,
that is correct.
The funny thing is, that I've never copied my externals to this folder in one
of my older versions, but never got this warning. (obviously I'd copied the
relevant files to my standalone manually)
Thanks
Tiemo
-Ursprüngliche Nachricht-
Von: use-livecode
Hello Matthias,
that is correct.
The funny thing is, that I've never copied my externals to this folder in one
of my older versions, but never got this warning. (obviously I'd copied the
relevant files to my standalone manually)
Thanks
Tiemo
-Ursprüngliche Nachricht-
Von: use-livecode
To be honest, if “always being able to launch standalone” is a concern for the
developer, then they shouldn’t be using the Starter Plan.
In my understanding the Starter Plan is a personal experience, it is available
so that one can learn programming and use it to build their own tools. If
