Hi davido,
Thanks for the quick reply
I believe if I use the ShortcutGadget, then I will need to get the end-user to configure the shortcuts themselves whenever they install my software, as it looks like I would need to use this to capture whatever the relevant shortcut is on their computer.
I believe the Windows API defines two keyboard constants: VK_ADD and VK_OEM_PLUS. My understanding is that VK_ADD is the "+" key on the numeric keypad, and VK_OEM_PLUS is the "+" key with the "=" sign.
Microsoft state in their documentation that VK_OEM_PLUS is valid for any country / region, so it seems that the "+" sign on the "=" key is available on all keyboards, and available as VK_OEM_PLUS.
If this is the case, then it would be nice for this same shortcut to be available from within PureBasic, and be cross-platform.
When I use the example in the PureBasic documentation on ShortcutGadget, and output the gadget state to the debug window, the value 65723 is returned for the "+" key on the "=" key (which is Shift + "=" on my UK keyboard). If I then use this value in AddKeyboardShortcut (instead of #PB_Shortcut_Add), then the shortcut works as I expect. However, I cannot assume that this numerical value would be valid for all keyboards.
I have tried using the constant #VK_OEM_PLUS which is already defined within PureBasic, but this has the value 187, so it appears it is not for use with AddKeyboardShortcut.
I hope you can see my dilemma
