Disabling all scopes turns everything on

[ptya]

Hi,
Just as I wrote my other issue I noticed a potential bug in the code. Now when you disable a scope, and there are no more enabled scopes after filtering, instead of turning everything off, the codes turns everything back on again. I don't think that is the intended usecase here.

[JohannesKlauss]

Thank you for reporting the issue. I'll release a fix for that

[JohannesKlauss]

This is actually intended behavior. If you disable all specific scopes the wildcard scope will be active which means all scopes are active. Although thinking about it this seems very counter intuitive and I might change that in a 4.1 version.

The initial reasoning behind this was, that all hotkeys work out of the box and if you need a specific focus on a component subtree you can activate a scope for the lifetime of that subtree.

Right now you can workaround by initially setting a scope none, which has no hotkeys assigned and never gets deactivated. This way only the active scopes are triggering.

[colinricardo]

@JohannesKlauss is there a recommended way of disabling all scopes? looping over the active scopes and calling disableScope doesn't seem to work