1.9.2 Custom shortcuts doesn't allow separate numpad keys
Posted: Sat Jul 12, 2025 1:25 pm
Problem:
Using version 1.9.2 I just realized XnView MP does not differenciate between numpad numbers and top row numbers.
This results in conflicts when the top row numbers are already assigned and less possible shortcuts to assign.
What I get:
When I set a shortcut "1" to be a one star rating and I press "numpad 1", the one star rating is applied.
The shortcut settings menu also only shows one, no matter if "1" or "numpad 1" is inserted.
What I expect:
As "1" isn't "numpad 1", they should be treated as two different keys. "numpad 1" should not trigger the one star rating.
Benefits:
You would have a higher number of possible key commands.
Differenciation between "1" and "numpad 1" would follow a standard other software already uses.
Using version 1.9.2 I just realized XnView MP does not differenciate between numpad numbers and top row numbers.
This results in conflicts when the top row numbers are already assigned and less possible shortcuts to assign.
What I get:
When I set a shortcut "1" to be a one star rating and I press "numpad 1", the one star rating is applied.
The shortcut settings menu also only shows one, no matter if "1" or "numpad 1" is inserted.
What I expect:
As "1" isn't "numpad 1", they should be treated as two different keys. "numpad 1" should not trigger the one star rating.
Benefits:
You would have a higher number of possible key commands.
Differenciation between "1" and "numpad 1" would follow a standard other software already uses.