I use icons and images that i put into a folder called External adjacent to my project.
I have a folder called Resources in my Project where these png files etc are stored or use them in the image editor…
However somehow some of the links to the png etc are still pointing to the downloads folder…
Now when i start my project i need to ‘search’ for these missing elements.
I locate the files and then proceed to continue to develop and save my project.
I exit the IDE come back in and yet again the same problem.
If you work with text files you can update the path to fix the problem.
If not, then you can select the image in your project and drag/drop the image again so the path gets fixed.
Just a simple advice about these two name (and namind things): be careful about name conficts.
Prefix them (or Suffix them) with a name related to the project / or with “shared” as a Prefix or as a Suffix.
For images and resources, and if your application name is Foo, I would use Foo_Images, Foo_Resources, and so on.
It will also be better for you to understand later.
And if you are unlucky and move a folder from its location, it will be easy to get it with a search for items starting with “Foo”…
No later than yesterday, I discovered a folder far away than where it belongs (I’ve moved it with other data - by error - there)..
I’ve had lots of issues with images and linked project files go missing when I copy a xojo project with the filesystem instead of using Save As. The Xojo IDE likes to save the paths relative to the project file so copying the project can break those links, while Saving As re-resolves them based on the new save location.
I have saved my project as xojo_code.
Because I like it for Git and I hoped this would help me find the instance of the image with an incorrect path or reference. Everything ‘in’ my project is internal..
I suspect the xojo_resources is where the issue is but it’s a binary file.
One trick to helping keep project links in-tact is to put the image resource inside the repository before you add it to Xojo. Then, once you drag it into Xojo, the relative path is inside the repository and relative to the project file. This works well for multi-user Git repositories. No more “this image exists at {co-author’s home path}” problems