Key Sequences Fail to Work When Advanced Configuration Page is Closed

Bugs or Unexpected Behavior
21

and the option is enabled for scrivener? (not for the CAG)?

22

Ah, this must be activated for Scrivener? Not for the CAG? Or for both?

If I activate it for both, it looks good. Sorry, I didn't understand that. I'll test it for a few days ... and thank you!

23

ah you are right, it needs to be enabled for both (while the CAG is inactive it will use the one configured for the app, when the cag is active it will use the one set on the CAG)

24

You say "the default polling interval is 1.5 seconds". Can I set this somewhere? I would like to experiment with 1 s. Or do you think that will kill the system?

25

1s would probably work fine as well.
You can enter this command in the terminal app to set it to 1s. You need to quit BTT first:

defaults write com.hegenberg.BetterTouchTool BTTAXPollingInterval 1
26

If Neil Armstrong had known "polling", he would have said: "This is a small step for a developer, but a big leap for the user."

Fields are now recognized correctly without exception! So far I haven't noticed any increase in cpu load.

@Andreas_Hegenberg BTT permanently checks which field the cursor is in every x seconds? I don't understand any of this but Is that necessary? Wouldn't it be easier to check the field with a new action, for example "check field" immediately before something is triggered?

27

For advanced trigger conditions I can do it like that (v4.517 - uploading)

However CAG's need to be active or inactive before something is triggered, because the triggers are not even loaded before a CAG is active.