The oddity that you describe may have something to do with other existing/reserved hotkey or Windows hotkey
For example, I have an AHK
(Auotohotkey) subroutine (script) that triggers a "peek under" functionality. The hotkey combination for this is an ON/OFF
toggle - CTRL+LEFTSHIFT+Alt+U
- which is quite complicated, so it's unlikely to be accidentally
pressed to invoke that subroutine. Each time the toggle is used, it triggers or untriggers the peek under function, which the function announces each time as a state change
, with the message "Peek under has just been enabled" or "Peek under has just been disabled".
So I was somewhat confused when peek under started being invoked without
my say-so. I eventually figured out that it was the Win+Left-Click
combo that was doing it (this is consistently repeatable). So AHK
was/is treating CTRL+LEFTSHIFT+Alt+U
as being equal to Win+Left-Click
. I feel sure there'll be an explanation somewhere for this equivalence, but I don't know what it is.How does this relate to LBC?
Well, another interesting thing is that, at the same time as peek under is being toggled, the LBC
drop-down menu will sometimes
also be toggled ON/OFF.
I normally toggle LBC
with the hotkey combo CTRL+LEFTSHIFT+Alt+L
- which is just one key different to the peek under hotkey. My experience is that LBC
has always been a pain as it inconsistently responds to the hotkeys set to invoke it, but I suspect it could be some kind of a priority interrupt or key buffer collision that is going on here, as there are some other odd things that I have separately raised regarding LBC
(which I don't think @mouser
has had time to get around to sorting out yet):
Couple of queries and an odd thing - using LBC v22.214.171.124 (2018-11-21)