Add context setting with particular virtual keys included/excluded

[Hibryda]

I'm still referring to my endavour with setting Orbweaver and other keyboards to work in unison and with maximum efficiency.

I miss one feature at the moment. As I mentioned in another entry, I'm working on an app allowing for visual hints on currently available key combinations and active VKs. And it would be helpful if particular VKs could be constrained only to specific device/app contexts. So, when leaving the context the keymapper would take care about putting them into disabled mode. Even better, if the keymapper could remember the last setting in the context as another boolean and restore it when returning to the context.
I know that VKs can be restrained just by defining them in the context, but here it's another story - it's about giving a feedback outside on currently available combinations.
Given the keymapper is already tracking context changes, it's easier this way than duplicating this tracking elsewhere.

P.S. I'm happy to see my suggestion on logging being applied and thus I'm not shy to propose more :D

[houmain]

So, when leaving the context the keymapper would take care about putting them into disabled mode

The virtual keys can be toggled when a context becomes active/inactive:

GPUpad = Virtual
Firefox = Virtual

[title = "GPUpad"]
ContextActive >> GPUpad ^ !GPUpad

[title = "Firefox"]
ContextActive >> Firefox ^ !Firefox

Your status indicator application could run keymapperctl like this and interpret its output:

keymapperctl --wait-toggled Any --is-pressed GPUpad --print " GPUpad=" --result --is-pressed Firefox --print " Firefox=" --result --print "\n" --restart

Note that in this case 0 means success. So it is 0 when the Context is active and 1 when it is not.