[Bug] keyboard mappings saga

[gitthangbaby]

Describe the bug

Shortcut capturing is soft in Windows. No support of WIN key, F13-F24 keys etc. ShareX, DeepL would interecept these keys.
This is a minor issue, as I just moved away from Crow -> DeepL -> QTranslate. Since simple modifier shortcuts are all taken, and even complex ones are taken, I now use keyboard Fn function to trigger F13-F24 keys.

The problem partially comes from default mappings in QTranslate. They use CTRL+key approach, which is conflicting with tons of apps. I'd advise against simple shortcuts as global, it's just unrealistic. There are ALL used locally. So as a user, I redfine global shortcuts to either CTRL+ALT+key, or even better, F13-F24 key on a Keychron like keyboard.

On the screenshot, it is visible I can define F14 combinations, but it's not intercepted. that is the "bug" here.

Second thing is disagreement with default shortcuts. Ctrl, Ctrl is of course a great shortcut and I love it can be combinaed with another shortcut.

Steps to reproduce

1. define shortcut F13 to F24 for an action in "Keyboard & Hotkeys" tab
2. press F13-F24

Expected behaviour

Action is performed

Actual behaviour

Action is not performed

QTranslate version

1.4.1

Java version

1.8.0_501

Operating system

Windows 11

Installed plugins (if relevant)

No response

Logs

Screenshots

[ahatem]

Thanks. I checked the implementation and confirmed the F13-F24 problem.

The shortcut recorder accepts these keys, but the global hotkey dependency currently used by QTranslate does not contain the later Windows mappings for F13-F24. This means the interface accepts a binding that the backend cannot register.

I will address F13-F24 registration and add Windows tests when I am back at my computer. Windows key support is separate and will need platform-specific handling.

You also make a good point about conflicts with modern applications. The current default bindings were chosen to match legacy QTranslate, so I do not want to simply replace them for everyone.

I think a better solution is to provide two selectable presets:

• Legacy QTranslate, preserving the current bindings
• Modern, with safer defaults that avoid common conflicts

Existing users would keep their current bindings after updating, and manually edited bindings would remain custom. I will keep the preset work separate from the F13-F24 registration fix because it needs its own design and cross-platform testing.