AutoHotkey Community

I currently have a macro that selects data from a system in order to determine if the value recorded matches any of the lines of data captured but it will not find a match and through testing I determined that because there are leading blanks (number of blanks depend on length of number) it is not finding the match. Here is what I have so far.

Use Trim() or OmitChars parameter in Parsing loop. Example:

By blanks, do you mean spaces? You could add a Regexreplace to your loop to remove all spaces at the beginning:



If you add this above your If statement, initial spaces should be cleared before the loopfield is evaluated by If.

As an alternative, you could add an InStr to your If statement:



Then, if PmtAmt is blurb, and A_Loopfield is " spacespaceblurbblahblah", If is true. InStr is faster than Regexmatch, so says the AHK help file.

There is a built-in command for that which is probably faster http://l.autohotkey.net/docs/commands/Trim.htm (and easier)

Ah! But I'm on AHK basic (scared that my scripts might break if I switch). So is everybody using AHK_L now? Or AHK2, even?—how is that taking off?

Re: basic v _l: There are various threads discussing this, but in general if your scripts don't use DLLCalls, or the basic COM you shouldn't have a problem upgrading. You can simply download the ZIP version http://l.autohotkey.net/ (scroll to DOWNLOAD, not click it at the top) I suggest the Unicode x86 version, but you could try the Ansi also which is just like basic with the new features added. If you try the unicode be sure to save your scripts as UTF-8 as that is a common mistake. You can try your scripts one by one by simply drag/drop them on the autohotkey.exe from the zip file you downloaded. V2 is still in progress so I wouldn't recommend taking the jump just yet, v2 will break all of your scripts due to syntax changes and also removed/replaced commands (for example StringReplace -> StrReplace to name but one)

@Guest: Thanks for your advice!! That is extremely useful. So a few more questions. If I pick up the _L version of the COM library somewhere, my scripts will work again? And what will happen if I use a script saved as ANSI with AHK_L Unicode?