On my screen (1680 * 1050) I don't even see the OK button. That message box needs a re-design or we need something that is better suited. The commands should be somehow grouped so that the ones belonging together are shown one below the other.
Perhaps we could use more messageboxes and each one shows only a certain group of switches and explanations? @laanwj Is a tabbed messagebox possible?
https://qt-project.org/doc/qt-4.8/qmessagebox.html
You can pass a setInformativeText / setDetailedText. The detailed text will be in a scrollable area, which is suited to this (show the main arguments in the main area, then expand for more details).
Only do this if you don't have to add too much code, I don't want to add a custom message box class (for example) for one rare case on one OS.
Maybe this is a good opportunity to move the help functionality out of AppInit2. We already want to move most of the initialization to another thread eventually, so it helps to split it to multiple parts. Arguments parsing should of course remain in the GUI (main) thread.
So I propose:
This also prevents having to add extra arguments to the ThreadSafeMessageBox call chain.
I've already tried a few things. It's the only workaround that works. It's an OS-level message box, there is no fine control over it. Any other workaround would amount to re-implementing the message box, which would be even more code and just not worth it.
Feel free to completely remove it though if the default width is fine on Windows.