Modifier-only hotkeys support

[plastikat]

I was wondering why modifier-only hotkeys (e.g. when keys like Ctrl or RAlt or LShift are pressed and released one at a time or in combination) are not allowed to be defined? Are there any technical restrictions?

It can sometimes be convenient, for example assigning RCtrl as a "Switch GUI focus" hotkey (which matches default VirtualBox "host key") and consequently spare yourself conceiving and learning yet another hotkey for a similar action.

Also the configuration dialog seems to generalize "left" or "right" modifiers (in spite of them being selectable in drop-down lists) to naïve ones (e.g. RCtrl to Ctrl). Is this intended and, if it is, then why?

[Maximus5]

That is by design of hotkeys processing. Yes, modifiers can't be used as single hotkeys.

I don't understand your question about left/right generalization...

[Maximus5]

That is by design of hotkeys processing. Yes, modifiers can't be used as single hotkeys.

I don't understand your question about left/right generalization...

[plastikat]

Yes, modifiers can't be used as single hotkeys.

Well, that's a pity. But not a show-stopper, of course.

I don't understand your question about left/right generalization...

Here's some additional details. I open a modifier drop-down list and click on RCtrl there. But, instead of this specific value, a naïve Ctrl (which is left/right agnostic) gets selected for the field.
It sometimes helps to resolve some hotkey conflicts or simply precludes false positives, when you bind one combination strictly to the "right" modifier (RCtrl+H, for example) and, optionally, another strictly to the "left" one (LCtrl+H); these combinations are then treated as distinct. I hope this provides some clarification.

[plastikat]

Yes, modifiers can't be used as single hotkeys.

Well, that's a pity. But not a show-stopper, of course.

I don't understand your question about left/right generalization...

Here's some additional details. I open a modifier drop-down list and click on RCtrl there. But, instead of this specific value, a naïve Ctrl (which is left/right agnostic) gets selected for the field.
It sometimes helps to resolve some hotkey conflicts or simply precludes false positives, when you bind one combination strictly to the "right" modifier (RCtrl+H, for example) and, optionally, another strictly to the "left" one (LCtrl+H); these combinations are then treated as distinct. I hope this provides some clarification.

[Maximus5]

You didn't say what action you have tried.
So I may only guess that its type is Global.
Than it's expected behavior due to WinAPI limitation.

[Maximus5]

You didn't say what action you have tried.
So I may only guess that its type is Global.
Than it's expected behavior due to WinAPI limitation.

[plastikat]

Thanks for the explanation about WinAPI restrictions. Initially I've observed the behavior with "Local" type, but at the time I didn't even think it's type-dependent...
I've done some additional tests and now I see that strict modifiers are still supported with "User" and "Macro" types, which is good to know.

[plastikat]

Thanks for the explanation about WinAPI restrictions. Initially I've observed the behavior with "Local" type, but at the time I didn't even think it's type-dependent...
I've done some additional tests and now I see that strict modifiers are still supported with "User" and "Macro" types, which is good to know.

[Maximus5]

Local uses same technique as Global, but Local hotkeys are deregistered when ConEmu is minimized for example.

[Maximus5]

Local uses same technique as Global, but Local hotkeys are deregistered when ConEmu is minimized for example.

[plastikat]

AFAICT this issue's subject is clear now, so to help the maintainer with his chores I am closing it. Please reopen if you disagree.

[plastikat]

AFAICT this issue's subject is clear now, so to help the maintainer with his chores I am closing it. Please reopen if you disagree.