The replace character function seems to remove spaces from the whole path rather than just the filename. Apologies for not noticing when you sent me the test version.
indeed it should replace just the filename. The directory path would be specified as the location physically on the computer that can be set by the user. With something like google drive, it's located at c:\users\google drive\folders with spaces\in the name\and so on. google drive, for example (and i'm sure the other cloud storage solutions out there), generally just give a random string to the folder in question that don't care about the folder tree preceeding it (or the name of the actual folder itself). you just share the folder in question and generate a link for it that looks like this https://googledrive.com/host/B1gLongR4nd0mNumb3R! regardless of the location in the actual google drive tree. thus the web link doesn't care about the spaces in the actual path on the computer.
I hope that makes sense. I think i've explained it quite badly but hopefully you can make sense of it.
Cheers :)
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I now moved the replacement and concatenation of the path to the filename so that replacement should only apply to the filename (and the parameter-generated path elements).
Oops! That's true and of course, it doesn't make sense.
BUt how should that function work then? Should only the file name be replaced?
indeed it should replace just the filename. The directory path would be specified as the location physically on the computer that can be set by the user. With something like google drive, it's located at c:\users\google drive\folders with spaces\in the name\and so on. google drive, for example (and i'm sure the other cloud storage solutions out there), generally just give a random string to the folder in question that don't care about the folder tree preceeding it (or the name of the actual folder itself). you just share the folder in question and generate a link for it that looks like this https://googledrive.com/host/B1gLongR4nd0mNumb3R! regardless of the location in the actual google drive tree. thus the web link doesn't care about the spaces in the actual path on the computer.
I hope that makes sense. I think i've explained it quite badly but hopefully you can make sense of it.
Cheers :)
David
Dear David,
thanks for your feedback!
I now moved the replacement and concatenation of the path to the filename so that replacement should only apply to the filename (and the parameter-generated path elements).
Try and let me know...