01-20-2017, 07:45 PM
> I've changed the logic so that it tries to find the file whose path has the most matching characters at the end. Hopefully this will eliminate the problem you described.
Yes, I think that's a good solution.
> It's perfectly valid to have two files with the same name but different case letters. Calls into the Android framework would fail if the case is wrong.
O.K., I have to solve that on my side of things. I'm syncing often with my Windows directories and have to watch out for the case sensitive stuff when I'm changing something.
But, am I right that your utility only fixes paths if it has found a file? At least if I'm using the manual replacement of the path, shouldn't there all links pointing to the old SD-card path be replaced, regardless if they point to a file or not?
It seems to me that isn't the case currently. And it would be much easier to just replace a missing file on the card or change the spelling to fix the missing file and not to have to run the path adjustment once again.
Yes, I think that's a good solution.
> It's perfectly valid to have two files with the same name but different case letters. Calls into the Android framework would fail if the case is wrong.
O.K., I have to solve that on my side of things. I'm syncing often with my Windows directories and have to watch out for the case sensitive stuff when I'm changing something.
But, am I right that your utility only fixes paths if it has found a file? At least if I'm using the manual replacement of the path, shouldn't there all links pointing to the old SD-card path be replaced, regardless if they point to a file or not?
It seems to me that isn't the case currently. And it would be much easier to just replace a missing file on the card or change the spelling to fix the missing file and not to have to run the path adjustment once again.