Change the behavior of "name is not valid" error
Posted: 14.12.2016, 13:26
I would like to request how illegal characters are handled by FreeCommander
Right now if the user happens to put in the name of the file or folder, for example a question mark, FC spits out error message and automatically reverts to the previous name. And that is annoying [at least for me], because it happens all the time. Typically when a long / complex title of a song / album / movie is copied, pasted as a file / folder name and modified to some extent- but not enough to be 100% valid. And so, all the work that was done in modifying a title is lost and has to be repeated
For example ACDSee 3.1 works in a user friendly way- it spits an error, but after clicking OK on the message box, it gets you right back to the file being changed [in the name changing mode] with those illegal characters still there
As for the more extended approach, those illegal characters could be highlighted with a user defined color. And if colors are implemented, there could also be an option for skipping the error message completely or just showing it for one second [so that there would be no need to move the pointer on the OK and clicking it]
Right now if the user happens to put in the name of the file or folder, for example a question mark, FC spits out error message and automatically reverts to the previous name. And that is annoying [at least for me], because it happens all the time. Typically when a long / complex title of a song / album / movie is copied, pasted as a file / folder name and modified to some extent- but not enough to be 100% valid. And so, all the work that was done in modifying a title is lost and has to be repeated
For example ACDSee 3.1 works in a user friendly way- it spits an error, but after clicking OK on the message box, it gets you right back to the file being changed [in the name changing mode] with those illegal characters still there
As for the more extended approach, those illegal characters could be highlighted with a user defined color. And if colors are implemented, there could also be an option for skipping the error message completely or just showing it for one second [so that there would be no need to move the pointer on the OK and clicking it]