What happened with CTRL+0 keybind on numpad?

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
goran.genter
Posts: 34
Joined: Fri 22 Aug 2014 16:28

What happened with CTRL+0 keybind on numpad?

Post by goran.genter » Mon 14 Jun 2021 21:00

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.

Raudar
Devart Team
Posts: 19
Joined: Fri 02 Apr 2021 11:04

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

Post by Raudar » Wed 16 Jun 2021 07:08

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

goran.genter
Posts: 34
Joined: Fri 22 Aug 2014 16:28

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

Post by goran.genter » Thu 16 Sep 2021 09:19

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.

alexa

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

Post by alexa » Fri 17 Sep 2021 15:40

We will investigate this issue and will answer you as soon as possible.

alexa

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

Post by alexa » Fri 17 Sep 2021 15:55

You would need to also hold SHIFT to make it work.

There was the same behavior in version 5.5.

Bjork
Posts: 1
Joined: Tue 21 Sep 2021 16:32

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

Post by Bjork » Wed 22 Sep 2021 06:08

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.
Last edited by Bjork on Mon 24 Jan 2022 19:16, edited 1 time in total.

alexa

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

Post by alexa » Wed 22 Sep 2021 10:01

Thank you for the reply.

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

Post Reply