This may be me not understanding the feature, and what amounts to a 'same type' keyboard; but when I first saw this feature, I was hoping I would be able to use it in a similar way to how I now end up using Karabiner; to configure shortcuts that would only execute when issued on my Razer Orbweaver keyboard, not when typed on my normal keyboard.
If this isn't actually a bug, and just me misunderstanding how 'Works on keyboards with same type' is meant to work; then consider this a feature request for being able to set a keyboard shortcut to only work when triggered from a certain device (it would be fine for my needs/use cases if this was only exposed through the advanced trigger conditions.
Mh that should definitely work, I use it all the time to remap e.g. Logitech buttons.
One restriction: it will not work if another app has taken exclusive lock /control over the keyboard (e.g. Karabiner Elements)
This is because then BTT needs to fall back to the higher level system API's, which don't allow to get the keyboard type.
Interesting.. I can't guarantee that I actually tested it properly before I used Karabiner; but I definitely noticed it not working when I tested just now (with Karabiner). I'll see if I can disable Karabiner and check again.
Is there any way to programatically check if something like Karabiner has an exclusive lock for the keyboard, and if so, show a warning/similar in BetterTouchTool?
It would also be really cool if the BetterTouchTool UI could show us some detail about what keyboard was used with that feature, so that we're able to know that it was set up correctly (ideally it would be a device name/type or similar)
@Andreas_Hegenberg Any chance of getting similar functionality added to BetterTouchTool so it can restrict mouse clicks to the device they were recorded on (similar to how we can do it for keyboard shortcuts)?