12-07-2021, 11:20 PM
Thanks Clarence - i'm well aware of the issues with upgrading the libraries (the first 10 times i fell for that gradually taught me the lesson lol)
I always download the libraries to a neutral location and copy them manually to where i want them to be so as to not overwrite existing folders that contain my files.
What i'm talking about is just randomly (no upgrade) my app stops working with the error that it can't find my custom library and it just seems to do a vanishing act. This has now happened several times, which is getting a bit weird.
The reason i've set it up this way is that i have a number of project folders and instead of replicating code in each app (and increasing risk of tiresome errors), i do this via my little custom library which resides inside CanelaDB and therefore always knows the relative path to the lib files and just loads them with 2 lines of code and keeps my working stack free of clutter.
And likewise with library upgrades, i just have the one central file to update with new checksums etc (well, 1 per project anyway)
This works very well for me - except for the mysterious vanishing act of the file. Initially i thought maybe it was something to do with time machine, but that doesn't make sense and copies of the same file in the same root directory are always unaffected. This happens literally between sessions of closing and opening the mainstack.
On further reflection i wonder if this may have something to do with my closeStack code. In this, i want to unload all stack files from memory then close the mainstack. I used the 'delete stack <stackName>' command as according to the documentation this removes stacks from memory and shouldn't actually delete them, but i wonder...
I always download the libraries to a neutral location and copy them manually to where i want them to be so as to not overwrite existing folders that contain my files.
What i'm talking about is just randomly (no upgrade) my app stops working with the error that it can't find my custom library and it just seems to do a vanishing act. This has now happened several times, which is getting a bit weird.
The reason i've set it up this way is that i have a number of project folders and instead of replicating code in each app (and increasing risk of tiresome errors), i do this via my little custom library which resides inside CanelaDB and therefore always knows the relative path to the lib files and just loads them with 2 lines of code and keeps my working stack free of clutter.
And likewise with library upgrades, i just have the one central file to update with new checksums etc (well, 1 per project anyway)
This works very well for me - except for the mysterious vanishing act of the file. Initially i thought maybe it was something to do with time machine, but that doesn't make sense and copies of the same file in the same root directory are always unaffected. This happens literally between sessions of closing and opening the mainstack.
On further reflection i wonder if this may have something to do with my closeStack code. In this, i want to unload all stack files from memory then close the mainstack. I used the 'delete stack <stackName>' command as according to the documentation this removes stacks from memory and shouldn't actually delete them, but i wonder...