I’m using Xojo 2022r1.1 on a Mac Arm 64 to develop a web project. My project is stored on a Windows server which I access using SMB. I use GraffitiSuite plugins in my project which requires a Copy Files build step to copy the scripts folder to the debug location every time I run the project.
Debugging across the network was slow since it was copying the script folder every time so I changed the Debug Destination folder to a local folder under /Users/MyUser/Xojo and put the scripts folder under /Users/MyUser/Xojo/Graffitisuite/scripts/ and dragged that folder into the copy step so it looks like this:
That all works fine and I am able to run the app. However, when I exit Xojo and go back in, the copy step shows in red and says:
This file could not be found - …/…/…/…/…/…/Users/MyUser/Xojo/Graffitisuite/
And I’m not able to run the app. If I delete that folder from the copy step and re-add it, everything works as expected. The relative path hasn’t changed so I don’t know why it can’t find the scripts folder after a restart.
Is there a way to specify an absolute path in the step such as "/Users/MyUser/Xojo/Graffitisuite/scripts/ rather than using the relative path to the app?
It is alright to store the project on OneDrive, but never run or work from there. Copy the project to your local drive, work on it, and when you are finished, send it back to the cloud.
Dropbox, OneDrive, etc: the locking necessary for syncing in these folders cause problems for the IDE. Don’t store your project there while you’re working on it.
Network drives: The IDE just doesn’t handle things not being readily available well, so if the share is locked or the connection is too slow or was dropped, you’re risking catastrophic data loss.
I can appreciate the warnings about working over a network share. I’m not a fan of git, to be honest, but I used to do what @Michel_Bujardet mentioned, copy the project down to which ever machine I was working on, edit and debug, and then copy it back up, until one day I accidentally copied up an old version over the current one. Fortunately I had a backup from the night before so I was able to restore but I still ended up losing several hours of work.
On my Windows workstation, the build step uses the absolute path instead of the relative path to the scripts folder and so it survives Xojo restarts. It’s only the Mac that has this issue. I was hoping to find a way to work around this.