This is the scenario: So, I have a downloaded ISO file and a matching downloaded checksum file in a specific folder. The checksum filename is the same as the ISO file but with a .md5 or .sha256 extension (I always do this for downloaded ISO files; good practice I think). My question is: Why does the verify checksum dialog unnecessarily expect me to navigate to the checksum file all over again? It seems to me, it should automatically look in the ISO file's folder and see that there is a checksum file with the same name and choose that file by default. Would save a lot of time. Just a suggestion. :-)
Example filenames: /Rod/DVD-CD_Images/kubuntu-14.04.4-desktop-amd64.iso /Rod/DVD-CD_Images/kubuntu-14.04.4-desktop-amd64.iso.sha256
Usage changed: you select the checksum file (containing the hashes) and start the dialog with it.
Git commit 2c5d47aed7c76679b5085a1fa8906d025524ceb8 by Alexander Bikadorov. Committed on 14/03/2017 at 20:05. Pushed by abikadorov into branch 'master'. Dialogs: rework of entire checksum dialog classes * Dialogs now QWizards. * Removed support for *deep tools. Standard tools can create/verify checksums in directories now. * Verify dialog should now be invoked with checksum file, not the files to check. Required for... * ...important bug fix: standard tools did not verify selected files, but only files in checksum file. M +1 -0 CMakeLists.txt M +1 -0 krusader/CMakeLists.txt M +410 -539 krusader/Dialogs/checksumdlg.cpp M +140 -48 krusader/Dialogs/checksumdlg.h M +0 -5 krusader/Konfigurator/kgdependencies.cpp M +0 -15 krusader/Konfigurator/krresulttable.cpp M +18 -35 krusader/Panel/panelfunc.cpp M +1 -0 krusader/Panel/panelfunc.h M +1 -2 krusader/krservices.cpp M +0 -3 krusader/krusader.cpp https://commits.kde.org/krusader/2c5d47aed7c76679b5085a1fa8906d025524ceb8