Leaderboard

I suggest to replace the syntax description StringReplace ( "string", "searchstring/start", "replacestring" [, occurrence = 0 [, casesense = 0]] ) with StringReplace ( "string", "searchstring"/start, "replacestring" [, occurrence = 0 [, casesense = 0]] ) This makes clear that parameter 2 is either a string to search for or an integer to be used as the starting position.

For general purpose the function it's good as it is. If someone needs something else or more info, the keyboard hooks or other windows APIs can provide additional data. The only code I'm going to figure it out this night will be this: ConsoleWrite(@YEAR & @CRLF)

Ahhh I see now. I understand so hard and I'm not even drunk. In this case it's a nice addition. I'll have some more tests. Just don't overprice them because you feel like a god.

It is consistent. The 0's mean that the key press got printed. The 1's mean that the key is still pressed but is not the first press. If the key is still held after a set time, well, repeat the keypress. Thanks but, I have nowhere the experience or knowledge to say that what I present, is without a doubt the best there is. It may very well be, but I'm not that god like in regards to code. I do present myself to my clients as god like, but is because I, in fact am, for them

For your specific case it's perfect, what I'm saying it's that probably it's not the best idea to change the actual _IsPressed() function since your proposed function it's working just in certain conditions. It might be better since it gives you additional info but not very consistent. Anyway I am happy that you posted because others might use this additional info so it's good to have another version of this function. You have plenty of good code around. I'll ask mods to delete all your posts if you will keep saying this in 2024. PS: this is how you know you are getting old, when there are like 5 minutes until this year will pass but you are too lazy for anything else and prefer to test random code

Okay. I seem to have missed an update for AutoItAutoComplete somewhere. The file I had was the problem?? Sorry about that.

What I guess I am saying is that I do not see the issue you report, so try to first figure out what steps to take to get this "wrong" calltip. The only way I was able to get it to go wrong is to force the calltip of ConsoleWrite before typing the ( after the StringInstr. So: Which what do I need to do to see your reported issue?