Just to update on this, everything is working perfectly for phrases and accents such as "à"... except on UWP apps such as Sticky Notes (Try àteu -> ateu). Notice how it adds a "backspace" if I use tab to select the replacement from suggestions. Strings without accent work as expe...

Thanks, this was a side effect of a Quick Find function. Should be corrected now - please download, re-install and let me know if it works. The error disappeared, but the command is still not working. Command 1 String: à postos Description: a postos Substitute: Menu, Tray, Icon TrayTip, Crase, Essa...

Great update, but it broke strings beginning with "à" (grave accented a). If it's followed by a space, I get this error on applay/save/load FK: If not followed by a space (i.e. apé -> apé), no error, but it also doesn't work. I also tried deleting and creating a command from scratch to eli...

Worked perfectly and it's easy to explain how to tweak. Look at the final version (except variable names): Main Send code, without line breaks and 2 variables: %INPUT__test%%INPUT__test2%%CODE_TestUpper% Command: first:=SubStr(INPUT__test,1,1) if first is upper Send, $u%INPUT__Test%:%INPUT__Test2%; ...

Hi again, New problem: I want to use input, but check if the first letter is capital or not and use the appropriate tag. Ex: $T%INPUT_test%:%INPUT_test2%; ; if first letters are lowercase $t%INPUT_test%:%INPUT_test2%; ; if first letters are uppercase I tried using Insert Command Code, but I can't ge...

There is definitely something weird going on. First I thought it was gaming apps or other overlay stuff (DisplayFusion and Geforce Experience). So I tested this on a LG Gram and also on a Surface Pro 3. Same issue. Then I tried using only Autohotkey... same issue. Later I tried ditching the diacriti...

No. It didn't work. How is this possible?
Is there any log I could send to investigate this further?
This is more frustrating because you don't have this issue :O

Hi again, Thanks for the email but it didn't work also. I tried on 3 different computers... same problem. BUT I SOLVED IT! The problem was the app used for testing: Sticky Notes 2017-10-25_07-35-08.gif I always tested in it. Since it's not a common misspelling, I ended up not checking this on other ...

It was disabled. It's a fresh trial install. I even didn't restore my backup. I also tried raw text and putting à in {à}. Alsto tried with a regular keyboard, since I'm using ergodox. :/

Just clean installed Windows latest and after drivers, Office and MemoQ (all not executing), Fastkey still doesn't work for: à postos > a postos BUT, it works for p or > por ???? Is the diacritic causing any issues? Maybe that time it worked it was my autohotkey in the background, not Fastkeys?