I have made a ton of different BTT shortcuts for various Mac apps, but Ableton Live seems to react different. Shortcuts do work fine, but when filling out any text fields in a project (like tracknames), the program types the conversions of the keys I have programmed in BTT. Is there some ingenious way for BTT to circumvent this?
what exactly do you mean by conversions?
As an example, Zooming shortcuts in Ableton are +/-. I used BTT to change that into R/T, which works fine, but as soon as I type a word in a text field that contains the characters R or T, these will get written as +/-
If I understand correctly, the exact name of a field does not matter in your case. It is only a matter of distinguishing text fields from non-text fields. Then take a look here
Sorry if I wasn't clear in my question.
In the screenshot you see a track in Ableton that I wanted to rename into 'BART'. Because I programmed triggers for R and T in BTT, those keycommands will be taken by Ableton as +/-. But I don't want that to happen in text fields. Does that make the issue more clear?
So when the cursor is in a text field, the letters should be typed. But if not, zoom should be active. This should work with the script if you find a menu item that can only be selected in a text field.
Ok now I understand the idea of using menu items. But the scripting seems a bit like a rabbit hole so I will just live with Ableton's standard keycommands. Thanks anyway
I use "Advanced conditions" in cases like the one you describe.
If you use a condition like "focused_element_subrole == "AXTextField" you can tell to BTT to not trigger the zoom if you press R or T inside a text field.
1 Like
Thanks @jordikt , I get the idea and although basic Advanced Conditions is just within my comprehension, scripting is certainly not. So I think I leave the idea of custom keycommands for Ableton.
Life is letting go:)