When right-clicking on a row in the Output box, there should be an option "Compare to clipboard" which compares the selected hash to the string that is currently saved in the user's clipboard, showing whether they match or not.

• Add "Export to Json" to Output's tool button
• Structure:

{
    "FileHasherUI.exe": {
        "filePath": "C:/Dev/Cpp/FileHasher/GUI/build-FileHasherUI-Qt_15_5_0_Static-Release/release/FileHasherUI.exe",
        "fileSizeKB": 12228,
        "hashes": {
            "MD5": "bc7f5871a70ab13d5882a4a5b45fc7b9",
            "SHA256": "831f73f1693a9778bccb17e5063372817d3e65abd6164854c2a44315418861f2",
            "SHA512": "c0b087228352f4350e30b30fb7e906a455a6689409e89662786fde8bd575ecd5e1b27f8482e7016d10229e2f1919d8d752cb95e43180f158e8d0696a30f84a99"
        }
    }
}

• Will need to change the Controller's cache to an unordered map

It isn't obvious or easily understandable that the Export buttons will export the content to the user's clipboard.
Exporting to the clipboard is currently also the only available option, which may make sense for the C-Array but not so much for JSON.
It would be better if upon clicking on "Export as ...", a new window would open, containing the following:

• A textbox containing the exported string
• A "Copy to Clipboard" button
• A "Save as" button that would prompt the user to save the content as a file

This would make it clearer where the exported data ends up, aswell as make it easier to add an Export to file functionality.
What would need to be done:

• Make a new window (.ui file, etc...)
• Let this window be opened upon clicking any "Export as ..." button
• Implement a "save to file" functionality, also letting the user choose the path and filename

Reproduce:

• Add file to file list
• Select hashing algorithms
• Remove / Rename file from disk (not from the GUI's file list)
• Click on Generate hashes

The monitoring thread never finishes and the GUI becomes unusable, needs to be killed via Task Manager.

The GUI currently doesn't react properly if errors happen in the background.
For example, the background will return an empty string on error.
The Hashing thread should be able to report errors to the Controller.
This won't be achievable for the Monitoring thread since that one will be blocking. This could be solved by:

• having a timeout, if after a set amount of time the Monitoring thread does not register any progress, it aborts
• letting the Backend set the process bytes to the file size, this would let the Monitoring thread terminate correctly, the error would then be handled by the Hashing thread

Since QProgressBar only takes signed 32 integers as in QProgressBar::minimum(), QProgressBar::maximum() and QProgressBar::value(), these methods should not be used. Instead, the percentage should be calculated separately (with 64 bit unsigned integers) and then set the percentage with QProgressBar::setFormat() even though this is not the intended way.

Programm becomes unusable after trying to hash a file with 0 bytes in size.

Steps to reproduce:

1. create an empty txt file
2. add that file to the hash list
3. click generate hash
4. programm will freeze and not be able to generate any further hashes