AutoHotkey Community

[Chris]

Thanks for mentioning it. I messed up when doing a single tiny change. It's fixed now.

[zorglups]

I have a Belgian/French keyboard and use only one language layout on my XP installation.

With the following simple script, I can reproduce the problem.

[Chris]

Thanks for the detailed post. I switched to Belgian/French layout and I can produce this problem too.

This should be fixed in the next update (probably tomorrow). Thanks.

[Chris]

Thanks to you and /Torben's earlier report, I think this has been fixed in today's release.

[zorglups]

Chris, I'm working in a support team and we are fighting really hard to get customer satisfaction by solving the calls as fast as possible.

I think we are a good team.

But you beat all of us.

I never saw a so fast, openminded and entousiastic support.

Thank you to you for your wonderfull application and for listening to us.

Pierre.

[zorglups]

I forgot to confirm that your last release solves the problem.

Pierre.

[Chris]

Thanks for the follow-up.

[Henrique]

Hi all,

I'm brazilian and our keyboard layout provides 3 deadkeys.

I want to "reprogram" all of them; I'll discuss one of them here (the deadkey for the tilde accent).

We have the following situation: that deadkey is only allowed by the OS to be combined with "a" and "o": "ã Ã õ Õ".

(Well, it seems that someone at Microsoft thinks that we brazilians speak spanish, so we can also combine the tilde deadkey with "n" to echo "ñ"...)

Anyway, I intend to "reprogram" that deadkey in such a way that it could also make combinations with other letters, such as "e", for instance.

However, if I try to make a combination with a non-valid letter, this is what I get: "~e". As all of you owners of keyboards which provide deadkeys know, it has always been this way, since those old Windows 3.x days. If I try to make a non-valid combination, I get the accent echoed along with the non-valid letter. (I'm using WinXP Pro SP2 now.)

Then, I found out about AutoHotkey and made the following attempts:

[First attempt]
:c*?:~e::{ASC 7869}

It works; however, the previous letter is deleted. Weird.
1) I type "test"
2) Then, I type "ẽ" and the last letter is deleted: "tesẽ".
3) It gets worse: if I try to type "ẽ" again, the cursor overwrites the very same letter and doesn't move forward. It gets stuck. (Any other letter is regularly echoed in the screen as usual and the cursor moves ahead normally.) So, it's not a valid solution.

[Second attempt]
:c*?:~~e::{ASC 7869}

It works:
1) I type "test"
2) Then, I type the tilde deadkey TWICE, I have two tildes echoed on the screen and, when I type "e", the two former tilde accents are deleted and an "ẽ" is echoed on the screen.

Good, but I have to press the deadkey TWICE. That's counter-productive if I have to type long texts. I want to be able to press the tilde deadkey only once and then type "e", just like I do with "a" or "o".

[Third attempt]
:b0c*?:~e::{BS 2}{ASC 7869}

It works:
1) I type "test"
2) Then, I type the tilde deadkey ONLY ONCE and, when I type "e", I have "testẽ" correctly echoed on the screen. No deleted letters, no faulty behaviour. Fine. But...

... I notice that the screen flashes on me, because AutoHotkey echoes on the screen (as quickly as possible) the tilde, the letter "e", then it deletes both characters, then it echoes "ẽ". This screen flashing is a huge discomfort when you remember that a text processor is all about a white page under black letters and the screen keeps flashing on my face every time I make a combination like that.

My question is: Is there a way to simply cause the OS to disregard the tilde deadkey as a deadkey? That way, I would simply type <~> + <e> and AutoHotkey would provide "ẽ" without any flashing.

I have tried...
SC028::Send {ASC 126}

...And it works. The deadkey is "not dead" anymore. I press it and it echoes "~". However, if I do that, I go back to "ground zero" because I can no longer type "ẽ". The solution found in the third attempt does not work anymore.

Thanks,
Henrique

[d-man]

[Henrique]

Thanks d-man,

it was almost OK:

[d-man]

Henrique: No I don’t know, it works for me, but you should post this under ”ask for help“ as your own topic, it is quite buried here, not sure people will see it.

[Chris]

I'm not sure, but I think the above belongs in this topic. In any case, I'll check into it in case it's something that can be fixed. Thanks for all the details.

[Chris]

I believe this issue has been fixed in today's v1.0.44.09. I think the problem boiled down to this:
Fixed one too many backspaces in asterisk hotstrings whose next-to-last character is a dead key.

Thanks for reporting it.

[Henrique]

Perfect, Chris!

Thank you,
Henrique

[chessa]