Feedback for devs: VkbCfg- Physical capabilities on logical buttons
Posted: Fri Mar 25, 2022 4:05
No doubt the capabilities of the VKB config software are vast and with the kind help from knowledgeable forum members, layered / multi-function mappings can be implemented, such as the one I got help on here recently: viewtopic.php?f=27&t=6361. So now, I am _very_ grateful I can have a tempo function on a shifted layer.
However, I'd like to ask the devs to consider improving the workflow of assigning physical button capabilities (ButtonAlt, tempo... etc) to the logical slots. It seems to me that the current final solution (linked in the post above) using a network of intermediate physical, boolean and logical mappings where some buttons need to be invisible to DirectX, would be difficult for new users to grasp. Particularly when some requirements (related to DirectX buttons and the boolean tab itself) are not covered in the manual - at least not that I have seen
However, I'd like to ask the devs to consider improving the workflow of assigning physical button capabilities (ButtonAlt, tempo... etc) to the logical slots. It seems to me that the current final solution (linked in the post above) using a network of intermediate physical, boolean and logical mappings where some buttons need to be invisible to DirectX, would be difficult for new users to grasp. Particularly when some requirements (related to DirectX buttons and the boolean tab itself) are not covered in the manual - at least not that I have seen