Save SHA and MD5 creation settings and change default mask
Moderators: white, Hacker, petermad, Stefan2
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
Save SHA and MD5 creation settings and change default mask
Thank a lot for such wonderful program!
There are two suggestions which hopefully can help make TC better. Both of them are related to CRC creation.
1) Ability to save "Create separate SFV files for each file" last state in wincmd.ini.
2) CRC filename should be constructed as filename + extension + crc-extension.
Suppose we have two files: Lion.avi and Lion.srt.
Checksums for them should be named Lion.avi.sha and Lion.srt.sha.
I know that this can be achieved by using *.*.sha mask instead of the default *.sha, but the mask is not saved for the future use, and it is annoying to put it by hands every time.
Thank you!
There are two suggestions which hopefully can help make TC better. Both of them are related to CRC creation.
1) Ability to save "Create separate SFV files for each file" last state in wincmd.ini.
2) CRC filename should be constructed as filename + extension + crc-extension.
Suppose we have two files: Lion.avi and Lion.srt.
Checksums for them should be named Lion.avi.sha and Lion.srt.sha.
I know that this can be achieved by using *.*.sha mask instead of the default *.sha, but the mask is not saved for the future use, and it is annoying to put it by hands every time.
Thank you!
Last edited by AndrewCreator on 2011-10-22, 11:19 UTC, edited 2 times in total.
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
- sqa_wizard
- Power Member
- Posts: 3864
- Joined: 2003-02-06, 11:41 UTC
- Location: Germany
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
- sqa_wizard
- Power Member
- Posts: 3864
- Joined: 2003-02-06, 11:41 UTC
- Location: Germany
Well searching for e.g. "Create separate SFV files for each file" has just 2 hits, one of them is TC Behaviour which will not be changed - CRC-Creation on directory of Sep 20, 2011 covering point 2)
#5767 Personal license
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
That's probably because no one promised this change for beta 8. ;)
But I must agree with your suggestion. If fact, the whole checksum dialog deserves update. Starting with that famous confusing way how to select algorithm (MD5 and SHA1 checkboxes behaving like radio buttons and SFV not really mentioned anywhere, but selected by unchecking both).
If selected checksum type is saved, then why not also save the state of checkbox for using separate files? Selecting it over and over again is not any less annoying than selecting checksum type over and over again would be. They are equally important, but one is saved, while the other isn't. Strange.
Saving of mask is a little more complicated. It's not possible to automatically save the string from file name field (e.g. c:\path\to\some.md5), because it would not make sense elsewhere. It would probably require separate option for default file mask. I once thought using *.*.ext would be good idea for myself, but it's simply not feasible to rewrite it every single time. Perhaps the best solution could be some simple template/profile system which would allow to define several favourite settings like:
- create md5 checksums and save them into one file "my favorite checksums name.md5"
- create md5 checksums and save them into one file "<parent dir name>.md5"
- create md5 checksums and save them into separate files "<file name>.<file extension>.md5"
- create sfv checksums and save them info one file "%any_variable%.sfv"
- etc...
I mean something really flexible (the above is only quick thought). Because currently if user wants anything other than defaults (e.g. I often like to save per-directory checksums in file "crc.sfv"), it means endless retyping or the same thing.
But I must agree with your suggestion. If fact, the whole checksum dialog deserves update. Starting with that famous confusing way how to select algorithm (MD5 and SHA1 checkboxes behaving like radio buttons and SFV not really mentioned anywhere, but selected by unchecking both).
If selected checksum type is saved, then why not also save the state of checkbox for using separate files? Selecting it over and over again is not any less annoying than selecting checksum type over and over again would be. They are equally important, but one is saved, while the other isn't. Strange.
Saving of mask is a little more complicated. It's not possible to automatically save the string from file name field (e.g. c:\path\to\some.md5), because it would not make sense elsewhere. It would probably require separate option for default file mask. I once thought using *.*.ext would be good idea for myself, but it's simply not feasible to rewrite it every single time. Perhaps the best solution could be some simple template/profile system which would allow to define several favourite settings like:
- create md5 checksums and save them into one file "my favorite checksums name.md5"
- create md5 checksums and save them into one file "<parent dir name>.md5"
- create md5 checksums and save them into separate files "<file name>.<file extension>.md5"
- create sfv checksums and save them info one file "%any_variable%.sfv"
- etc...
I mean something really flexible (the above is only quick thought). Because currently if user wants anything other than defaults (e.g. I often like to save per-directory checksums in file "crc.sfv"), it means endless retyping or the same thing.
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
Sob, thank you for the detailed answer.
I will try to summarize:
1) "Separate files" option should be saved.
2) Checksum type options should be turned to radio buttons or the ability to select more than one checksum type should be added.
3) SVF type should be shown.
Currently used checksum file name creation way is quite logical except of file extension is ignored. Therefore I think that it will be enough add the ability to include file extension. This can be implemented as option for backward compatibility. So,
4) Ability to include file extension.
I will try to summarize:
1) "Separate files" option should be saved.
2) Checksum type options should be turned to radio buttons or the ability to select more than one checksum type should be added.
3) SVF type should be shown.
Currently used checksum file name creation way is quite logical except of file extension is ignored. Therefore I think that it will be enough add the ability to include file extension. This can be implemented as option for backward compatibility. So,
4) Ability to include file extension.
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
-
- Member
- Posts: 122
- Joined: 2011-10-10, 23:25 UTC
- ghisler(Author)
- Site Admin
- Posts: 48125
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I will add it to my wish list. I think that a switch similar to the AppendLnk switch would do.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com