#969 CodeBlocks blocking keyboard combo: WIN+[key]

[kyle]

CodeBlocks 20.03 x64
Windows 10 1909 x64

When the CodeBlocks application has window focus,
the following key-combination is blocked:
CTRL+WIN+NUMPAD[number]

I require this key combo to switch virtual desktops.
CodeBlocks should not block any WIN+(key) combos

[Teodor Petrov]

@kyle: Have you tried some older release? Is the problem observable there? What happens if the focus is not on the editor, but on some other UI element.

@pecanh Do you know if this might be related to the keybinder?

[bluehazzard]

For me on windows 10 this does not do anything?
If i enable numpad and use

shift + win + 8, 4 , 6, 2, is the same as shift + win + arrow keys
this works in codeblocks, like outside of codeblocks

ctrl + win + 1,2,3,4
does nothing in codeblocks, and also nothing outside of codeblocks

ctrl + win + arrow keys
switches desktops, works in codeblocks like outside of codeblocks

Do you have some other things enabled?

[pecan]

How do you set a windows hotkey for CTRL+WIN+NUMPAD[number] so I can investigate the problem.

[pecan]

Using a virgin copy of windows 10 (not running Codeblocks)
Ctrl+Win+Numlock(ON)+anyNumKeyPad key will NOT switch desktops.
Ctrl+Win+Numlock(OFF)+anyNumKeyPadArrowKey WILL behave as advertised for Windows 10.
But Numlock must be OFF to switch desktops.

This may be related to a bug in CodeBlocks 17 (and prior versions) which allowed keybindings when numlock was ON.
This bug is still in Codeblocks 20. I will fix it soon. So please remove any keybinding in CodeBlocks that were set with Numlock ON. That should solve your problem.

A keybinding that was set with numlock on will contain a non-ascii character. Like a non-english character. See image below. Use Menu->Settings->Editor->KeyboardShortcuts to remove the binding.

https://sourceforge.net/p/codeblocks/tickets/_discuss/thread/8397da107d/c53a/attachment/keybinding.png

[kyle]

Aha,
Yes, I tried to test, and sure it was non-response specific to Numpad without NumLock.
So the issue it not C::B at all.

Thank you all for advice

The issue ticket here is void, how do I close it?

[pecan]

This ticket needs to be closed.
pecan.