Also just an additional note:
It is fairly clear to me now that the original intent was to have the full source folder in the Directory property and only the filename in the Filename property (or else why would you have had two properties? If you intended for full path you would not likely have called the property Filename but rather SourcePath or something)
The Directory property as described above does not work correctly. And while you changed the Filename property to now contain the full path so that there's at least always useful data now, I am wondering if actually the best approach would be to fix both to work as they were originally intended?
In other words, the bug may not have been as I described in my first post (where I didn't even realize there was a Directory property). The bug actually may not have been that Filename did NOT contain the full path on download, but that it DID contain the full path on upload. The bug was probably that Filename contained the full path when referencing local files. Combined with the bug that the Directory property does not show the correct directory. If the Directory property correctly shows only the full directory on both local and server and the Filename property contains only the filename on both local and server, then that would also solve this and probably be more in line with what you originally intended. Tho I also still personally think you should just scrap both and make a SourcePath and TargetPath property where the SourcePath contains the full source path (just like Filename is NOW working after your change) and the TargetPath contains the full target path.
In any event, I don't really care now cause all I really needed was to know the full target path and with the full source path in Filename combined with the Translate functions, I can get the target path, but I just am posting this for your consideration.
It is fairly clear to me now that the original intent was to have the full source folder in the Directory property and only the filename in the Filename property (or else why would you have had two properties? If you intended for full path you would not likely have called the property Filename but rather SourcePath or something)
The Directory property as described above does not work correctly. And while you changed the Filename property to now contain the full path so that there's at least always useful data now, I am wondering if actually the best approach would be to fix both to work as they were originally intended?
In other words, the bug may not have been as I described in my first post (where I didn't even realize there was a Directory property). The bug actually may not have been that Filename did NOT contain the full path on download, but that it DID contain the full path on upload. The bug was probably that Filename contained the full path when referencing local files. Combined with the bug that the Directory property does not show the correct directory. If the Directory property correctly shows only the full directory on both local and server and the Filename property contains only the filename on both local and server, then that would also solve this and probably be more in line with what you originally intended. Tho I also still personally think you should just scrap both and make a SourcePath and TargetPath property where the SourcePath contains the full source path (just like Filename is NOW working after your change) and the TargetPath contains the full target path.
In any event, I don't really care now cause all I really needed was to know the full target path and with the full source path in Filename combined with the Translate functions, I can get the target path, but I just am posting this for your consideration.