Or map F12 to screenshot.... in case that was missed in my original post.
Yes, that is another option, the only problem I can see with that is it involves going into each PakSet each time an update is made, and updating menuconf.tab.
Yeah, don't use the v4 w32api releases. You'll find many other nasty surprises eventually too - console failure, random linker errors with GDI and Bzip2, and on and on. But, SDL2.02 changed something making it incompatible with older MinGW, and MS changed sometime making Windows incompatible with SDL2.01. Lucky MSYS2 MinGW sticks with the working v3 w32api, and also works with current SDL2. v4 w32api is a steaming pile of...
Thanks for the info, I will take a look at what version of MinGW & SDL2 I am using (I think I was using SDL 2.00 simply beacuse I already had the MinGW version downloaded on my computer).
-- UPDATE: Tried using MSYS2, and ended up with a couple of additional dll dependencies, compared to MSYS - (libwinpthread-1.dll, libbz2-1.dll) --
The answer is easy: include help under the save icon and use F1 as a shortcut to help (like in most programs?).
F1 is already mapped to the general Help system, "Unmapped Keys" are linked specifically to Keyboard Help.
For the time being I will manually patch and build the SDL2 version for Steam, until a decision has been made on this (or a similar patch).