That is happening when selecting which way to go.
I tried so many things on 3 devices throughout the day, but I did not take systemtic notes. My recollection is:
- if there is a map that is bigger than the free space, then you cannot go there. Even if you move between places on the same storage. Seems you do copy/delete pairs, not a linux style mv. The documentation should warn about that scenario, or Locus should even tell which file that is (because I think Locus knows the details, because the grand total cannot trigger a no-go).
- if you have maps or mapsVectoron on extSD and chose have the main folder on intSD, then there is a good chance that the combined size will not fit into intSD (there is a reason people use extSDs :-)
Here I propose that you leave any file on the storage where it is before, only move to private space.
A user can easily comprehend that, because they moved maps (raster and/or vector) to different places in the firts place.
My bottom line from hours of testing today ...
Cheers
Michael
I tried so many things on 3 devices throughout the day, but I did not take systemtic notes. My recollection is:
- if there is a map that is bigger than the free space, then you cannot go there. Even if you move between places on the same storage. Seems you do copy/delete pairs, not a linux style mv. The documentation should warn about that scenario, or Locus should even tell which file that is (because I think Locus knows the details, because the grand total cannot trigger a no-go).
- if you have maps or mapsVectoron on extSD and chose have the main folder on intSD, then there is a good chance that the combined size will not fit into intSD (there is a reason people use extSDs :-)
Here I propose that you leave any file on the storage where it is before, only move to private space.
A user can easily comprehend that, because they moved maps (raster and/or vector) to different places in the firts place.
My bottom line from hours of testing today ...
Cheers
Michael