Is your feature request related to a problem? Please describe.
Second level keybindings seems to not be implemented. I have had configured my mouse using Logitech software to use one of the keys as a "shift" key, which adds another layer of key bindings. After a simple change of LED settings through Piper the second layer bindings are non present - there is no reaction on pressing them. Piper doesn't seem to have interface to configure the second layer of bindings anyway.
Describe the solution you'd like
The best solution would be to fully implement second layer of keybindings - for supported devices add button in GUI which allows to set second layer of bindings (like in Logitech software).
Describe alternatives you've considered
If full implementation is not an option piper should at least not overwrite existing bindings on the second layer to none or show some information about that because now from user perspective setting a minor improvement ends in major deterioration of experience.
Additional context
My mouse on which problem occurs is Logitech G502 Hero. Piper recognizes the "second level" button, yet this functionality ends at it.
Is your feature request related to a problem? Please describe. Second level keybindings seems to not be implemented. I have had configured my mouse using Logitech software to use one of the keys as a "shift" key, which adds another layer of key bindings. After a simple change of LED settings through Piper the second layer bindings are non present - there is no reaction on pressing them. Piper doesn't seem to have interface to configure the second layer of bindings anyway.
Describe the solution you'd like The best solution would be to fully implement second layer of keybindings - for supported devices add button in GUI which allows to set second layer of bindings (like in Logitech software).
Describe alternatives you've considered If full implementation is not an option piper should at least not overwrite existing bindings on the second layer to none or show some information about that because now from user perspective setting a minor improvement ends in major deterioration of experience.
Additional context My mouse on which problem occurs is Logitech G502 Hero. Piper recognizes the "second level" button, yet this functionality ends at it.