I use my MacBook with an external keyboard. Sadly the keyboard has some weird quirks and the top row (F keys) does not correspond to the Mac’s special keys.
Now I want to press the same key (F4 but in that keyboard hard wired to cmd+H) for both Mission Control and Launchpad, and depending on press duration either of these get’s called.
This works nicely; I followed the official tutorial on that.
I also use the “works only on the same type of keyboard” condition.
However every time I come back to the office and put my keyboard back in (I don’t use it in wireless configuration, but wired only) BTT does not recognize the keyboard anymore, and my nicely set up triggers do not work.
As you can guess this is tiresome.
I do not want the other built-in keyboard to trigger the action.
what kind of keyboard is this? I could only imagine it reporting different serial numbers / ids every time you connect it - although that would be quite weird.
Interestingly enough this time the shortcuts still worked after un- and replugging the keyboard.
Mhh, maybe it’s worse than I thought and it just happens randomly that it stops working.
It could be related to secure input mode. If some app (e.g. a password manager) forgets to disable that mode, or if you have configured your terminal app to use secure input mode, then many of BTT's keyboard related features can not work (including keyboard detection).
Another solution would be to have different BTT presets for your different work / keyboard environments and activate them on demand, then you wouldn't necessarily need keyboard detection.
But I think I do not use that mode (at least deliberately). I use iterm2, but I have not enabled the secure input. However I see that the option to use the old detection feature when secure input happens is on – could this be the culprit? Because I could now just see it the shortcut fail randomly over the work day.
Different presets… yeah could be a thing to try out, but honestly just sounds like a hassle I’d like to avoid.
