Page 1 of 1

What happened with CTRL+0 keybind on numpad?

Posted: Mon 14 Jun 2021 21:00
by goran.genter
In version 5 in DataEditor mode I usually set something to null value by pressing CTRL+0 (and I mean pressing 0 on numpad). But in version 6 I can only get it to work with 0 in numbers row. I can't even make my own keybind because numpad keypresses are not recognized at all.

Re: What happened with CTRL+0 keybind on numpad?

Posted: Wed 16 Jun 2021 07:08
by Raudar
Hi Goran,

Thanks for the flag, our team is going to fix this logic.

Once it's done we will release a new build available for download.

Best regards,
Victor

Re: What happened with CTRL+0 keybind on numpad?

Posted: Thu 16 Sep 2021 09:19
by goran.genter
This is mentioned in the list of bug fixes:

Handling of CTRL + 0 on the numeric keyboard (p194936)

but it still doesn't work for me. Only CTRL+0 in normal numbers row work, not in numpad.

Re: What happened with CTRL+0 keybind on numpad?

Posted: Fri 17 Sep 2021 15:40
by alexa
We will investigate this issue and will answer you as soon as possible.

Re: What happened with CTRL+0 keybind on numpad?

Posted: Fri 17 Sep 2021 15:55
by alexa
You would need to also hold SHIFT to make it work.

There was the same behavior in version 5.5.

Re: What happened with CTRL+0 keybind on numpad?

Posted: Wed 22 Sep 2021 06:08
by Bjork
he default behaviour of the shift key in windows is to disable the NumLock state if it's turned on. In order to use the modifier with the numpad keys you will need some way to stop this behaviour from occurring. Programs such as AutoHotKey can be used to stop this behaviour but the opinion on whether this is safe too use seems to be mixed and I am not sure on Blizzard's stance on this. Alternatively you can leave numlock turned off and map the keys to shift+numpad end, shift+numpad downarrow etc. instead.

Re: What happened with CTRL+0 keybind on numpad?

Posted: Wed 22 Sep 2021 10:01
by alexa
Thank you for the reply.

We will fix it in one of the next product versions.