Applied. The relevant changes will be merged to 2.2.2.
Yes! (if i interprete the patch file right): that matches exactly the workaround i would have proposed:
A patch does not need interpreting. It represents the change exactly. The tool chain supports that exact information, meaning patches can be generated and applied easily.
You really must learn to use the development branch "main" and to work with patches.
Everybody involved in the development (as you are now) really has to do it. It is super-easy. Did you even try?
Now I had to dig the suggested changes from long forum threads etc.
Merge requests in GitLab are an alternative to patches. I personally don't like them. Typically a merge request is associated with a bug report, thus splitting the relevant information into 2 places. To test a merge request I must download the changes as a patch and apply it. A patch uploaded into the original bug report would make more sense.
Trivial changes can be merged without testing by clicking a "Merge" button. Then a merge request is useful but those cases are rare.
Thus, a good old patch is still recommended.
I understood the iteration of selected ListView items could be optimized further. If you do it, please open a new report and attach a patch.