Open GoogleCodeExporter opened 8 years ago
This is not a bug, it is intentional. You can manualy rename file when
uploading new revision. The key thing is that it is expected many users could
access document and changing filename could cause troubles to match local
copies. So manual renaming is required to approve intention.
Original comment by vit.jo...@gmail.com
on 25 Oct 2011 at 11:01
Summary of email with detailed and screenshots
I understand that you want the name to be changed explicitly, but perhaps you
can improve it:
1) Keeping the file name why not. But could you at least consider updating the
file extension? If I upload a PDF, the default would be to get a PDF when I
download. As it is now, it remains an XLS if it’s an XLS I uploaded first.
Meaning that if I’m not very careful, I won’t be able to open my file
anymore after I download it, and I may think it has been corrupted. Can you by
default keep the name, but change the extension?
2) Can you add a button somewhere with “Update name to match new content”
or something like that?
3) Or add a check box, checked by default, with “Keep file name”?
This way, by default the name is kept, but if the user explicitly uncheck
“Keep file name”, then it would use the name of the New Content instead, or
with the button solution, by default it keeps the name, or the user can
manually edit the name to whatever he likes, or if he click on the button, he
get the correct new name and extension? It doesn’t seem much, but believe me,
I tried the manual edit solution, and with long file path / file name and short
editbox, it’s not easy to be sure you copied it right! And anyway, manual
copy should be avoided as much as possible to limit human error.
Original comment by da...@aeroinsys.com
on 25 Oct 2011 at 11:44
OK. I will try to improve behavior based on previous suggestions
Original comment by vit.jo...@gmail.com
on 25 Oct 2011 at 9:13
Original issue reported on code.google.com by
da...@aeroinsys.com
on 25 Oct 2011 at 9:00