11-12-2020, 03:02 AM
Thanks Mark,
I'm on Catalina, haven't made a move to big sur just yet - hadn't figured on notarisation, you may well be right - but on the other hand, the app shouldn't run at all if that were the case?
This attempt was an interim build to test something with the local database.
At present i sync cloud -> local on login... bit of a delay starting up, but subsequent actions much quicker. But on quit, the local DB seems to disappear - is that meant to be the case or am i doing something wrong?
It very much makes sense not to store the database inside the app bundle, and places like app support, documents or preferences seem a much better place for the SDK to reside. I had asked that exact question a while back anticipating this kind of issue but think that question just fizzled out and i didn't pursue it...
I know the documentation section on this will be updated at some point, but in the mean time, is the general idea that on first run the app will copy the SDK folder to a writeable destination? Not sure LCM does that at present, i could find no CanelaSoftware folder in either my /Library/Application Support/ or my ~/Library/Application Support/ folders, but it there is a copy of this inside the LCM app bundle at /Contents/Resources/_MacOS/data/config/CanelaDB.
Not sure where the specialFolderPath("support") is used?
Anyway will keep working on the app inside LiveCode and will revisit this at some point later...
I'm on Catalina, haven't made a move to big sur just yet - hadn't figured on notarisation, you may well be right - but on the other hand, the app shouldn't run at all if that were the case?
This attempt was an interim build to test something with the local database.
At present i sync cloud -> local on login... bit of a delay starting up, but subsequent actions much quicker. But on quit, the local DB seems to disappear - is that meant to be the case or am i doing something wrong?
It very much makes sense not to store the database inside the app bundle, and places like app support, documents or preferences seem a much better place for the SDK to reside. I had asked that exact question a while back anticipating this kind of issue but think that question just fizzled out and i didn't pursue it...
I know the documentation section on this will be updated at some point, but in the mean time, is the general idea that on first run the app will copy the SDK folder to a writeable destination? Not sure LCM does that at present, i could find no CanelaSoftware folder in either my /Library/Application Support/ or my ~/Library/Application Support/ folders, but it there is a copy of this inside the LCM app bundle at /Contents/Resources/_MacOS/data/config/CanelaDB.
Not sure where the specialFolderPath("support") is used?
Anyway will keep working on the app inside LiveCode and will revisit this at some point later...