Raival-e
[Feature] Checksum Verification
Add an additional "Copy Checksum" button within the "File Properties" dialog window. Subsequently, when opening the "File Properties" window for another file, the checksum verification result should be automatically displayed.
btw you can copy any of the properties by long clicking the value field.
I understand, but my focus is on automated comparison🤔
Don't think this is needed we already have the hashes you can just see and compare them visually if you're opening the properties for both files anyway 🤔
Don't think this is needed we already have the hashes you can just see and compare them visually if you're opening the properties for both files anyway 🤔
But... the 'Properties' window doesn't have an edit box for me to paste the checksum of the file I want to compare against. How exactly am I supposed to visually compare them side-by-side?
But... the 'Properties' window doesn't have an edit box for me to paste the checksum of the file I want to compare against. How exactly am I supposed to visually compare them side-by-side?
By looking at first and last 4 characters? That's how I usually do, plus if you refer to SHA256 it does not have any collisions.
@XiaoluoFoxington I didn't mean side by side, you can just memorize 8 characters
But... the 'Properties' window doesn't have an edit box for me to paste the checksum of the file I want to compare against. How exactly am I supposed to visually compare them side-by-side?
By looking at first and last 4 characters? That's how I usually do, plus if you refer to SHA256 it does not have any collisions.
@XiaoluoFoxington I didn't mean side by side, you can just memorize 8 characters
Now you don't have to deliberately memorize them at all — isn't that way better?
isn't that way better?
Depends. Is it worth the memory overhead? Because every time you open properties of a file it will make that check. Maybe a greedy string match could help...
@Raival-e what do you think?
isn't that way better?
Depends. Is it worth the memory overhead? Because every time you open properties of a file it will make that check. Maybe a greedy string match could help...
@Raival-e what do you think?
No, my idea is that the check would only be performed when you've previously clicked "Copy Checksum" in the Properties window, and then open another file's Properties.
Compare checksum is common in file managers (Material Files, MT Manager, etc), and pretty easy to implement too. It will be added, but probably not in v1.3.2 as I'm focusing on bug fixes.
Compare checksum is common in file managers (Material Files, MT Manager, etc), and pretty easy to implement too. It will be added, but probably not in v1.3.2 as I'm focusing on bug fixes.
If this is being planned, how about we consider a feature to detect duplicate files? This obviously requires calculating checksum of all the files but is geared to serve better to a file explorer. That way you can check for more than 1 duplicates and don't have to manually do the above mentioned process. Just discussing the feasibility, a simple checksum checker can also just be done instead if there are no plans for a full-fletched de-duplicator.
It is possible, but never seen similar feature before.
I swear Google files had something in the clean up section. Can't make it come up atm, will update here.
nvm even Samsung Files can detect duplicate files, but I never thought of using checksum.
I swear Google files had something in the clean up section. Can't make it come up atm, will update here.
https://github.com/user-attachments/assets/4bd26baf-d4d0-4ed1-85a5-689c67c0957e
To make this efficient, we could make it run a routine let's say every week to detect dupes. And allow for optional manual checks instead of having it index every file on the fs constantly