I am trying to create a shortcut to map ^C to ⌘C. However I want it to work everywhere except in the Terminal. So I created a Conditional Activation Group with the following criteria:
However that doesn't seem to work either, at least not consistently. I do notice that this particular shortcut has a blue line instead of a green one. What does that mean? And why wouldn't it be working?
@Andreas_Hegenberg is there any way to pay for premium support, or anything like that? The issues (like this one) I've been having with BTT lately have been really frustrating mainly because I'm not sure what I'm doing wrong.
Unfortunately I don't really have an idea, your setup looks ok (and I just tried here with a similar setup). Could any other app conflict? Maybe something triggering on ctrl+c?
Can you check whether your shortcut is showing up as expected in the "Recently Used" section.
The blue / green line just shows which preset your trigger is in (hover the line to see), as long as that preset is enabled that doesn't matter.
With reference to your second screenshot @xidiot , what does r^⇧C mean? In other words, what exactly is that mapped to?
Also @Andreas_Hegenberg , it is not showing up in Recently Used. And it's not just this one shortcut... it's EVERY shortcut mapped in the Conditional Activation Group. I've also got one that re-maps ^A to ⌘A and that one isn't being triggered either.
Lastly, I saw another weird glitch when I was cleaning up presets. After deleting an unused preset, the Conditional Activation Group (which was definitely NOT a part of that preset!) disappeared completely. It was just totally gone from the left pane. So then I created a new Activation Group with the same criteria, and as soon as I did that, all of the shortcuts I had previously saved in the CAG reappeared.
I'm starting to think it might be worthwhile for me to totally uninstall BTT and reinstall it. But does this leave behind any data folders that I should also clean up?
That usually means the CAG was created when that unused preset was still the master preset. Was this preset still enabled or was it disabled?
to completely reset BTT, delete this folder:
~/Library/Application Support/BetterTouchTool
(go there via Finder => Go => Go to Folder, make sure to include the ~)
Even after doing a clean reinstall of BTT, and then painstakingly recreating all my triggers manuall, my ^C shortcut in the Conditional Activation Group (along with others) is still not working. I am attaching an export of all my triggers. Could anybody see if they can recreate this same problem? triggers.bttpreset (99.8 KB)
I continue to have problems with any triggers I set up inside of Conditional Activation Groups. They don't work and I feel increasingly confident that this is a bug in BTT and not merely a case of Secure Input being activated or any other situational problem. I am highly motivated to help figure this issue out, so I am wondering if there are any logs, screen recordings, diagnostic data, or anything else I could provide to help pinpoint the root cause? Please let me know as I really depend on BetterTouchTool but not being able to utilize keyboard shortcuts inside of CAGs is a major bummer.
in the recent alphas (5.322) I fixed the issue that prevented them from working under secure input mode and/or with the old keyboard shortcut implementation. Maybe that fixes your issue?
