Deactivated triggers cause problems

@Andreas_Hegenberg I've had the suspicion several times that deactivated triggers prevent activated ones from working. I now have a concrete example. Maybe that will help. Only deletion ensures that everything works as expected.

This deactivated, app-specific trigger

[
{
"BTTActionCategory" : 0,
"BTTLastUpdatedAt" : 1717838302.9892778,
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "DAFF777F-A158-4FE4-8245-E75E6673B27C",
"BTTPredefinedActionType" : 124,
"BTTPredefinedActionName" : "MenĂźleisten Element aktivieren",
"BTTMenubarPath" : "Darstellung;Miniaturansichten in der Tableiste anzeigen",
"BTTAdditionalConfiguration" : "0",
"BTTKeyboardShortcutKeyboardType" : 5771,
"BTTTriggerOnDown" : 1,
"BTTLayoutIndependentChar" : "§",
"BTTEnabled" : 0,
"BTTEnabled2" : 1,
"BTTShortcutKeyCode" : 10,
"BTTShortcutModifierKeys" : 0,
"BTTOrder" : 52,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTGestureNotes" : "Tableiste ein/aus"
}
]

has prevented this trigger from working (for all apps)

[
{
"BTTActionCategory" : 0,
"BTTLastUpdatedAt" : 1736932158.884361,
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "780EB746-D4E8-446E-9D9D-6AEBC26EAE30",
"BTTPredefinedActionType" : 366,
"BTTPredefinedActionName" : "Leerer Platzhalter",
"BTTAdditionalConfiguration" : "0",
"BTTKeyboardShortcutKeyboardType" : 3809,
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 1,
"BTTLayoutIndependentChar" : "§",
"BTTEnabled" : 1,
"BTTEnabled2" : 1,
"BTTShortcutKeyCode" : 10,
"BTTShortcutModifierKeys" : 0,
"BTTOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTAdditionalActions" : [
{
"BTTActionCategory" : 0,
"BTTLastUpdatedAt" : 1736932126.3959951,
"BTTTriggerParentUUID" : "780EB746-D4E8-446E-9D9D-6AEBC26EAE30",
"BTTIsPureAction" : true,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "E80864EC-0746-412B-B74A-D56F0F5F34AB",
"BTTPredefinedActionType" : 177,
"BTTPredefinedActionName" : "Zeige or Verstecke spezifische Anwendung",
"BTTAppToShowOrHide" : "/System/Applications/Stickies.app",
"BTTShowHideAppConfig" : "{"BTTShowHideSpecificAppMoveToSpace":"BTTShowHideSpecificAppHiddenToCurrentSpace","BTTShowHideSpecificAppOnlyShow":false,"BTTShowHideSpecificAppOnlyHide":false,"BTTShowHideSpecificAffectedWindow":"BTTShowHideSpecificAppAffectLastUsedWindow","BTTShowHideSpecificMinimizeInstead":false,"BTTShowHideSpecificAppRegex":"","BTTShowHideSpecificAppOnlyTreatActiveAsVisible":true,"BTTShowHideSpecificAppOnlyIfRunning":false,"BTTShowHideSpecificAppCMDN":false,"BTTShowHideSpecificAppMoveToCurrentSpace":false,"BTTShowHideSpecificAppMoveAllToCurrentSpace":false}",
"BTTKeyboardShortcutKeyboardType" : 0,
"BTTEnabled" : 1,
"BTTEnabled2" : 1,
"BTTShortcutKeyCode" : -1,
"BTTOrder" : 4,
"BTTAutoAdaptToKeyboardLayout" : 0
}
],
"BTTGestureNotes" : "Stickies / Notizen show/hide"
}
]

It came back to my mind when I read this from another user:

"I originally thought it was conditional on how laggy my macOS was, but at the moment, I'm not having this issue again after modifying and deleting a few deactivated key sequence triggers for taking a screenshot."

Edit: I have another one. If you tell me what you need to look at it, I'll be happy to supply it. :slightly_smiling_face:

This is expected / legacy behavior:
https://docs.folivora.ai/docs/2_2_preferences_global_vs_app_specific.html#exclude-global-triggers-from-specific-apps

A deactivated app-specific trigger means that for this app the system default trigger will be used instead. Unfortunately many older setups make use of this (before CAGs were available), which is why I can not change it easily although I understand it might be confusing.
Maybe at some point I'll come up with a better solution.

Thanks, Andreas, hm, I'm not sure I understand this. :thinking:

If there is an enabled app specific trigger and an enabled global one, then the app specific one has priority.

Now if you deactivate the app specific one, then I would have expected the global one to take over. But the deactivated one is still “active”, but no longer does what it should, but passes to the system default, which prevents the global from working?

Good to know, but not easy to understand :slightly_smiling_face:

I have no idea, but would it change anything if you could put deactivated triggers in a “trash” (like in the Finder) and this trash would be "cut off" from the system?

you could create a trash CAG :wink:

And then you would have the “normal” behavior of deactivated triggers?

a deactivated trigger is just enabling the default behavior for a specific app or CAG, so if the CAG would never be active, the deactivated trigger won‘t cause issues

OK, so by a “trash CAG” you mean a CAG whose conditions are never met?

yep :+1:

1 Like

Would it be possible for BTT to also display deactivated triggers under “Recenty Used”, perhaps specially marked? That would help enormously to find them.

unfortunately I can't think of a way to do that. For deactivated keyboard shortcuts the events are not caught by BTT, thus no logic is run at the time you press the keys. This means BTT doesn't know whether you have recently (tried) to use it.

I see. Thank you!

I'll annoy you one last time :innocent:

Would it be possible to enter something like “only deactivated” (or a special character) in the search field of an app to show only deactivated triggers?