When I call any popup window (like RayCast or iTerm2 hotkey window) BTT continues to use bindings for application which was active before popup.
For example, I have application for which I map 'Enter' to 'V'. Open that application, then call RayCast with shortcut. RayCast window appears and I can't use 'Enter' in it because it is mapped to 'V'.
Device information:
this is not a bug, such windows do usually not change the active app. (this is intentional, they don’t want the other app to loose keyboard focus. Some of them have special modes to do that though )
However often you can use conditional activation groups in BTT to match such windows.
Have a look at the various options described in this thread:
Nice! But, if I understand correctly, I have to tune Conditional Activation Group for all shortcuts in all applications, which is lots of work! Seems like global exclusion condition would be much better.
I think you are thinking about „advanced trigger conditions“ - these would be per trigger. Conditional activation groups instead act globally (you can also make global exclusion lists using them): Trigger Conditions & Conditional Activation Groups · GitBook
I just tried it and Conditional Activation Groups don't seem to have "visible_window_list" condition (which works in advanced trigger conditions) and "Window Name" don't detect opening RayCast window.
usually window name is the best option. If raycast doesn’t have a window name this won’t work though.
However I think I can add one more condition to the CAGs that can match the focused accessibility element‘s app. This should help, I’ll look into that tomorrow.