command : make always bindings a choice per binding - #3112
Conversation
Remove the always_bindings category. Instead, make all other types of bindings configurable as `always`.
|
It is not clear what problem this might solve. Can you elaborate? |
Currently, you can only have a binding take place always (when another plugin is running, and when the screen is locked) that behaves like a regular binding. This allows having this « always » behaviour for repeatable and release bindings. |
|
Fwiw I think you could add a new category of bindings, which can have repeatable, always and release as boolean options instead of being separate lists. Then we say everything in the old options is deprecated and remove it after 1-2 releases. |
|
Also fwiw the ini syntax is ugly (not your fault, just how it is), if you have any better ideas of how to encode the information, that would be great. Maybe a command prefix of always$, repeat$, for ex. |
|
@ammen99 atfer some thinking, i have a one-line declaration syntax that is This would make a binding work for any of these modes, so for example, to take back the example of press-to-speak in the wiki, you’d have one toggle binding for both normal and release, and it would of course allow getting an Am i correct in my understanding that it’s fine to drop the « name » (so, And does this config syntax sound good to you ? |
3 participants
Remove the always_bindings category. Instead, make all other types of bindings configurable as
always.I don’t quite expect it to be merged as is, as it breaks configuration and might not be the cleanest/best way to do this, but i am looking for feedback/someone to have a better way of handling things.