10 replies to this topic

[hpk1908]

I have several hotstrings of the form:
:*:xxx::some text
these hotstrings have always worked perfectly. They erase the triggering string and replace it with the text without an ending character. Now, however, they all are doing the same strange thing. They type type all but the last characters of the triggering string and then erase the final characters of the replacement text, like this:
:*:xxx::this text
now produces this result:
xxthis te
or this:
:*:mygm::mymail@gmail.com
now gives:
mygmymail@gmail.
What in the world is going on! - help

[Leef_me]

Hi hpk1908, welcome to the forum.

First question: what changed ? New computer ? New version of AHk?

question two: are you trying to use something on a remote computer ?

third question: have you tried closing all running ahk scripts and opening just this one ?

question four: have you tried rebooting your computer?

[hpk1908]

Thanks for your reply.
First of all, I'm running the same version of autohotkey that I've always had and the same computer. I am only running one script and I have tried rebooting. The one thing that has been different since the hotstrings have been malfunctioning is that my computer was controlled remotely by a technician who was setting up our local network. We added a new computer and the AHK script doesn't return correct hotstrings on that computer either. I hope this helps. I really don't understand it.

[Leef_me]

We added a new computer

I'm not sure how that might affect your computer's operation.

The way AHk works for me is to use hotkeys and hotstrings on my local computer,
with the script running on my local computer.

Are you using Ahk in this same manner?
or are you trying to use it with a remote computer ?

At times I need to "log in" to a remote computer to edit files.
I have found that there is somewhat of a delay before keys, click and mousemoves are recognized.
I haven't tried, but don't think AHk would do well in this type of setup.


I've heard of systems where the local computer is primarily an interface,
All programs and data are "servered" from a main system that stores the applications and/or the data.
Is it possible that your system is something like this ?



Can you mak a copy of your original script and modify the hotstrings by removing the *
(so that an ending charcter is required) ?
Make sure only the modified version of the script is running and see what results you get.

[hpk1908]

I'm sorry if I didn't make it clear, but I am not running any computer remotely. There are two computers on our network, but I only use one at a time and most often the other computer is not even turned on. The only remote activity has been when the technician remotely controlled both machines when he was setting up the network. I have turned off the * option, but the only difference it made was that all the triggering string printed and it cut off the trailing characters of the replacement string. Something like this:
::*xy::printthis
result after typing the hot and an ending character:
*xyprintt
From the above, it looks like the B option is turned off ,but I also explicitly turned it on and it gave the same results.

[hpk1908]

I removed all scripts and just ran one script as you suggested. The script was:
::btw::by the way
here is what I get when I type the triggering string and follow it with a line feed: btwby the w

I just don't get it. they have always worked great before.

[Leef_me]

Two additional questions:
What version of AHk are you using?
Do you compile the script of just run the *.ahk version?

clipboard = version is %A_AhkVersion%
msgbox version is %A_AhkVersion%

Based in the effort and tests done, it seems like it is time to go back to the technician and ask "what did you do?"

[hpk1908]

Yes, I think you're right; that's what I'll do.

[hpk1908]

Thanks all, got it fixed now.