snippet triggering behavior not optimal

Note:
Before bug reporting, please make sure you have tried the latest (alpha) version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app's "Crash Reports" section.


Describe the bug
A clear and concise description of what the bug is. Any bug reports that contain insults against me or my software will be deleted without warning and the user will be blocked (unfortunately this has become necessary to mention here).

triggering a snippet text expansion by key sequence only works in some apps/fields and very inconsistently. Puts the feature at an unusable level practically.


Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):

mac keyboard


Screenshots
If applicable, add screenshots to help explain your problem. (You can just paste or drag them here)

na


Device information:

  • Type of Mac: m1 mbp
  • macOS version: 16.2
  • BetterTouchTool version: (please post the exact version - not just "the latest one") 6.011

Additional information (e.g. crash logs, related issues, etc.):

multi-year experience with typeitforme (deactivated): not perfect but works usable/much better

is there a workaround/setting to make the snippet text expansion triggering more reliable across the os/apps.

how are you using it? in general the paste text action works everywhere where you can paste text, you can also set it to type instead of paste then it will work everywhere but slower

can i enable debug logging when triggering it and send a log. looking the pains of typeit4me, text expansion is not a rundum sorglos thing.

unfortunately there are no logs for this, but maybe post some screenshots of your setup and describe where it does not work

ok here it is:

text expansion issue tests:
all in gmail compose/chrome regular release channel / no fancy extensions

behavior in various editors/os framework fields/editors appears to vary

a) trigger: ma

triggering 2 / 5 times

test@example.com

$ma

test@example.com

$ma

$ma

b) trigger: fmfg triggering 1 out 5 attempts

fmfg

fmfg

fmfg

fmfg

fmfg

c) trigger: fmfg 3 out 6 attempts triggered

Mit freundlichen Grüßen,

john doe

Mit freundlichen Grüßen,

john doe

fmfg

fmfg

fmfg

Mit freundlichen Grüßen,

john doe

d) trigger: mdb 2/4 triggering

Best, john

Best, john

e) trigger: lg 1/5 triggering

lg john doe

lg

lg

lg

lg

lg

f) trigger $gsm 1/3 triggering

+99 999 99999

$gsm

$gsm

g)

khg (triggering 4 out of 5 times)

OK: examplestreet 99/9

OK: examplestreet 99/9

OK: examplestreet 99/9

OK: examplestreet 99/9

NOK: khg

h) trigger $sg 1/3 success

Sehr geehrte Damen und Herren,

$sg

$sg

with config:

already done: try different triggers e.g. with/without leading $, re-clear/record the trigger sequence. there are no overloaded trigger strings from the os text expander, no other text expander hooked in.

I've now tried the OS text replacement functionality from gmail/chrome a compose contenteditable? field: 0 triggers on 2 snippets . works consistently with textedit (NSTextView?). User judgement: unusable, I want to use it consistently across apps and inputs.

Better post a screenshot of your key sequence setup, most issues are due to too small allowed timeouts and similar

$gsm below clear; record

0.3 may be too short :slight_smile:

Are you sure you can type all those characters in that time?

1 Like

googling it out of the several os apis for text expansion pain: CGEvent.tapCreate might be most current needing input monitoring permissions [ https://developer.apple.com/forums/thread/707680?answerId=716892022#716892022 ]

cudos: max pause between keystrokes: 1s
spot testing chrome/gmail, textedit, finder: OK

$wtf

WTF!!

good to close but there is no close option

after some time with it now - it does not work reliably: some key triggering snippets don't trigger with no clear pattern. workaround: clear/relearn the sequence (record-save).

re-learning does nothing if you record the same sequence again, however using proper timing values is crucial and depends a lot on how you are using key sequences. In general they are very reliable.

1 second could still be too short. Especially if you’re typing special characters and need to look at the keyboard.

Abbreviations don’t need to be long, just unique. This can be achieved, for example, with space space. So "Mit freundlichen Grüssen" could be shortened to fg space space. That’s short and unique because you never type two spaces after a word. And the spacebar is always directly under your thumb. And if you ever just want to write fg, you’d only press space once, so nothing would be triggered.