Num 0 counts as Insert when setting mouse button as keyboard shortcut.
Currently when you set a mouse button to Keyboard Shortcut, and use Num 0, it's actually acting as Insert instead, regardless of if num lock is on or not. It will show as Num 0 on the button, but will not type 0s.
Anonymous
shared this idea
-
Russell Gooday
commented
I can confirm this is an issue in Logi Options+ version 1.97.791262 on a window 11 system.
In my 3D software the numpad keys are used for various display options. The decimal point for instance toggles wireframe overlay, which is really handy to have assigned to a side mouse key when modelling.
In logioptions+ all assignments behave as if num-lock is off (regardless of whether it is or isn't) e.g. instead of 9 outputting 9, it performs page up or 3 performs page down.
I had a peek at the settings.db file, which contains json. With my back button set to 'NUM Decimal' i found the following code
"id": "card_global_presets_keyboard_shortcut",
"macro": {
"actionName": "keyboard_none",
"keystroke": {
"code": 99,
"displayCharacter": "NUM DECIMAL",
"virtualKeyId": "VK_DELETE"
},
"type": "KEYSTROKE"
},I'm guessing a bit here, but I believe virtualKeyId should be 'VK_decimal' not 'VK_delete' and the code should be 110 not 99.
It certainly looks like a clue to the issue.
To add that with my G502 lightspeed and G Hub there is not this issue. The numpad keys behave as expected e.g. a numpad decimal is a decimal or a 5 is a 5 etc.