6 replies to this topic

[/Torben]

When I use a script with a hotstring the keyboard behaves faulty:

The accents - acute (´), circumflex (^), grave (`), and (¨) – are all shown twice before the letter instead of over the letter:
So I get:
´´e instead of é
``e instead of è
^^e instead of ê
¨¨a instead of ä
The ~ is not shown at all.

As soon as I exit the script, the keyboard returns to normal functioning.

The problem does not occur when I use scripts without hotstrings.

I use a Danish keyboard

/Torben

[Chris]

Thanks for reporting this. I think I know the problem and will try to get it fixed soon.

[Chris]

I have updated the installer with a change that I hope will fix this. When you get a chance, please let me know if it's any better or worse. Thanks again.

http://www.autohotkey.com/download/

[/Torben]

Hello, Chris
I appreciate your efforts, so I hate so say that it’s all the same.
I downloaded the new version, but nothing has changed.
/Torben

[Chris]

Thanks for testing it. I've scoured the 'net and found some other possibilities that I will research.

Background: To support hotstrings, the keyboard hook calls a standard Windows function ToAscii(), which translates a virtual key code into its ASCII equivalent. However, it seems that this function has some nasty side-effects that are completely undocumented by MS. These side-effects interfere with keyboard layouts that use dead keys (diacritics).

[Chris]

Quick question: When you have a hotstring script running and you press a dead key, does the dead key appear immediately, or must you wait until you press the base/finishing key? If it appears immediately, does it appear twice immediately, or does its second appearance occur only when the base key is pressed?

Also, could you test this short script without any other scripts running:
sleep, 3000 ; give time to switch to an editor
Send ``e ; Use double-accent to mean a single literal accent.

Does it produce è?
Thanks.

[/Torben]

1. it appears twice immediately

2. Yes, it does produce an è

/Torben