any reason to store in documents instead of in library?
it seems like there might be less of a chance of the user misusing the
Files app to break the app.
On Thu, Feb 29, 2024 at 5:32 PM Mike Kerner
wrote:
> ah. that's a better way of handling this. i was going to have the app
> check the docume
ah. that's a better way of handling this. i was going to have the app check
the documents folder for updates, before loading a stack, but if i keep the
source stacks, there, it will work better.
On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
You can't add or change anything inside the app bundle so downloaded files
have to go in specialFolderPath("documents"). Copy the originals from the
resources folder to the documents folder on first launch so you always have
a known file path location. Any file in documents will be overwritten w
i haven't tried deploying to a device, yet, so bear with me:
when you load the updated stack/behavior/etc., are you saving it into the
app bundle, or elsewhere? on locked/single-app devices, persistence is the
thing (but i would imagine that it works the same on single-app devices as
it does for no
