Maniphest T101955

Huion KD100 - incorrect programmable keys reading
Needs Triage, Normal
Actions

Assigned To
None
Authored By
Adam Dera (rimau)
Oct 20 2022, 8:12 PM
Tags
  • BF Blender
Subscribers
Adam Dera (rimau)
Germano Cavalcante (mano-wii)
Omar Emara (OmarSquircleArt)

Description

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 27.20.100.8477

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: rBb292cfe5a936
Worked: (newest version of Blender that worked as expected)

Short description of error
Hi, I got a Huion KD100 Mini Keydial and Blender seems to be the only software not regonizzing it's programmable keys correctly. I have set it up as Numpad keys, but Blender does not recognize the assigments, reading the keystroke values for Num Lock off. Affinity Designer, Photo, Google docs, everything else recognizes the defined keys, even with app profiles. Sadly Blender does not as the only one.

Exact steps for others to reproduce the error
The only step here is really to hook up a configured KD100 and trying to change the view. Can also be easily verified in the Preferences section by testing the key bindings.
I would be more than happy to test/debug further with my device if that's helpful.

Event Timeline

Adam Dera (rimau) created this task.Oct 20 2022, 8:12 PM
Omar Emara (OmarSquircleArt) changed the task status from Needs Triage to Needs Information from User.Oct 24 2022, 5:22 PM
Omar Emara (OmarSquircleArt) added a subscriber: Omar Emara (OmarSquircleArt).

What do you mean by "reading the keystroke values for Num Lock off."? All the programmable keys are interpreted as the Num Lock key?

Adam Dera (rimau) added a comment.Oct 24 2022, 10:16 PM

Hi :)

Sorry, this might have been confusing. So the readings equal to the values of the keys with the Num Lock set to 'off'. So this gives always arrows, PgUp, PgDwn, etc. This happens for the keys with a double function with NumLock, the keys like Enter, +, - etc work normally with their single functions.

I did test with the NumLock on the main keyboard both set to on and off. Regardless of that setting, all other apps read the assigned values, Blender always reads the values for NumLock 'off' state. Assiging other functions to the KD100 keys works correctly, including multiple key shortcuts.

Thanks,
Adam

Omar Emara (OmarSquircleArt) changed the task status from Needs Information from User to Needs Triage.Oct 25 2022, 10:28 AM
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Oct 25 2022, 3:13 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).
In T101955#1436817, @Adam Dera (rimau) wrote:

Sorry, this might have been confusing. So the readings equal to the values of the keys with the Num Lock set to 'off'. So this gives always arrows, PgUp, PgDwn, etc. This happens for the keys with a double function with NumLock, the keys like Enter, +, - etc work normally with their single functions.

I did test with the NumLock on the main keyboard both set to on and off. Regardless of that setting, all other apps read the assigned values, Blender always reads the values for NumLock 'off' state. Assiging other functions to the KD100 keys works correctly, including multiple key shortcuts.

Thanks,
Adam

NumLock state is not considered for shortcuts in Blender. The Numpad 2 key activates the same operation in Blender no matter if NumLock is activated or not.
The only places NumLock will have an effect in Blender are the areas where you type some text.

When you try to assign a shortcut with the Huion KD100 Mini Keydial what key appears?

Adam Dera (rimau) added a comment.Oct 25 2022, 7:03 PM

Hi,

I am not trying to use NumLock as a shrotcut, I'm reffering to the NumLock on/off state as per the LED light on the keyboard. The problem is that when I assign the keys to the shortcuts they show the values of Arrow Keys, Ins, Del, PgUp, PgDwn (that's the NumLock off state values for that keys)... while the KD100 setup app, and all other apps read values: Numpad1, Numpad2, etc...

It is a very strange bahavior indeed, as these keys don't even have these values as default. They are fully programmable. Maybe the case that Blender is ignoring the NumLock state for viewport controls is actually causing this dissconection with the driver.

Adam Dera (rimau) added a comment.Oct 26 2022, 10:50 PM

Hi,

I have tested the KD100 on MacOS, and it worked just fine. Key assigments where all correct.

Germano Cavalcante (mano-wii) changed the task status from Needs Information from User to Needs Triage.Nov 30 2022, 2:49 PM