@ngraham I have in the meantime switched away from KDE, so it would be difficult for me to continue the development...

Is there a way to separate this class to its own file? Or is it some convention in this project to have these huge files?

Won't using the blocking versions block the UI as well?... that's why I chose to use the non blocking versions and just update the UI once the work is finished by the other threads.

Screen out the cached algorithms beforehand

Fix mutex placement and add show cached checksum values when combobox value is changed

Capture item path by value

Format algorithm values in combobox.

Reverted back to the combobox based layout

Ou, ok. Sorry, I didn't know that. Perfect, so combobox it is then.

I can revert it back to the combobox based layout. Don't we have some UX people that could take a look at this?

@anthonyfieroni, @elvisangelaccio, @colomar any progress? just want to get a status... this diff seems to be taking quite a long time to get reviewed after making changes...

Small code tweaks, nothing that changes functionality

I reverted back to the group box layout and parallelized hash calculations (removed the annoying recursive function).

I am still not clear on what to do now. Should I revert it to be a lot of separate buttons (hidden in a collapsible group box) (as @elvisangelaccio said) or should I keep it in a dropdown (ok according to me and @anthonyfieroni)?... I'm going to fix some other stuff in the meantime. I also made this verifyChecksumRecursive function to verify the checksums serially (one after another)(because up to 2 algorithms can be candidates for certain checksum inputs) to not consume too much resources. I'm thinking of doing that in parallel instead. Do you think it's a good idea? Are there any guidelines for these situations?

Convert to only combobox based layout

I will also need help figuring out what config to use for storing the users last used hash algorithm from the combobox (if we go that route).

A possible combobox layout

KIO repository

It is kinda questionable as far as what are the most common hash algorithms. I most often use SHA512 for example. I think having only the combobox would be ok for me, but I'm not a UX person. So just let me know if you figure out anything else.

I'm going to give that a try.

Place advanced algorithms into KCollapsibleGroupBox

I am new to KDE development and I want to use the KCollapsibleGroupBox but I don't know how. Are there any plugins for Qt Designer for KWidgetsAddons?

I agree that the layout is not optimal. I'm going to try to optimize it now.

Remove C++17 features