AutoHotkey Community

Each employee has a UID. There are six different teams of employees. If agent A belong to group 1, then MsgBox out something. If agent B belongs to group 2, msg box somethign else out. 6 teams, 6 different messages, 6 different if/if-else statments.

So I have a section in my GUI script that uses a variable for the UID agenst a list.

Is there a limit on how many characters you can have in a "else if(char_limit_in_here?)"

Using my 6 sets of ID's; group 1, has 38 id's, group 2 has 78, group 3 has 38 ect... but group 6 has almost 400 ID's, The script works if I break up group 6 into smaller if/else statments, but does not work when I have all 400 in one large else if() command.

Is this accurate?

I sugget using if Var in MatchList
http://www.autohotkey.com/docs/commands/IfIn.htm

As a referrence, there are almost 4800 characters in the 'big' else/if statment.

[ guiOpID = "xzy" ] x 370 ID's = 4800 +/- characters within the else if ( here)



------
Edit, You posted when I did, I will look into the match list now.

Thanks!

Something like this? Or does the E001 through E405 need ""s or %%'s, I still get confused with when to sue them, the link doesnt have any syntax around the car name. But I wanted to check.

Hmm...I can't see any reason why this wouldn't work:



As long as the bounds are strictly alphanumeric I believe the function should understand what's within them. You can try that.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

I used 'B004' as an example, they unfortunitly are not in any order.

ID's are as follows: 23Y, A04 0Ou, UvI, vVu, 4PF, FF0, FFo, FFO, ectectect.

No real order or anything, no patterns. 23Y and A04 may be in the same group. So sadly the 'bewteen' is not an option.

Are the IDs that are in each group every day the same? And do you have a means by which you can extract the member IDs of each group into a list?

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

The ID's stay the same from 'day to day', we may add/remove Id's as time goes on though. Generally the ID's come in excel format, but have info 'before' the OpId.

I have:




When my script encounters the OpId, to make its first choice on action, it only needs to process the '23y' or 'U0X' part of it. When we get the entire list of OpID's, they come to use in like 'NNJ23Y' 'CNJU0X' 'NATV1234', but only the last 3 digits of the OpId are of use to me/us.

Well it will be best to find a way to isolate the data you need somehow. If you can copy the data for each group from Excel to individual text files, you can run a file-reading loop when you start your script to save the data you need into match lists, something like this (assuming that all the IDs are listed vertically in one column of the spreadsheet):



Then you can run the if [var] in statements with the appropriate match lists:



Now if group 6 is the only large group, you can just skip saving its contents to var and just use the logical inference that if it isn't in any of the other 5 groups, it must be in group 6:

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

I love your enthusiasm Sinkfaze, honestly

I like the idea of 'defualting' the group 6 to the last 'else' statement, but besides the "6 groups", we have a '7th group'. Group 7 is every single OTHER employee (80,000+ lol), besieds the few hundred special ID's.

so group 1, 2, 3 , 4, 5 and 6 have special rules, we use the script to tell which group they are in and thus which action. The final else is 'group 7' which is the everyday employee who have no special rules.



I don't know. This has grown overly complicated.


I was able to cut the long 'group 6' into smaller if/else statements, making a group 6A, 6B, 6C, 6D...all belong to the same 'group', but it is broken into 30-40 ID sections vs the 400+ Id's in one section.

It's not the cleanest work around, but tested and works for now.


I was just kind of curious if there was a character limit or whitespace limit inside the '(' and ')'s.

So if we assume, for example, you have groups 6A through 6J, you might also be able to use a loop to check all of them rather than creating a long string of if a OR b OR c...:







Your company has nearly 90K employees, I'm surprised you thought it wouldn't get complicated.



I'm getting an opportunity to do some small-scale testing implementing AHK on machines at my place of work, if successful I'm going to lead a project for a much larger implementation. I'm trying to take advantage of any opportunity I can get to solve AHK problems in a work-related environment to hone my skills, so don't expect that I'll give up easily.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

The limitations I know of are:

• Each line of script may be up to 16384 characters. Note that in the following example, there is only one "line":
  
  Code:
  If (x = A
      or x = B)
  
• Each expression can have no more than 512 tokens. Each operator (open/close parenthesis, 'or', '=', etc.) or operand (variable or function reference, literal string, number, etc.) counts as one token. For instance, in the code above there are 9 tokens.
• There can be no more than 512 derefs (variable references or function calls), but the above limit will typically be reached first.

Btw,...should be...

That would be it then.

That makes sense, considering how many '=' and 'or's I have in there.

Poo.

Why not create 6 text files with the three special employee codes, you could use an excel macro, or ahk. Whether a space, comma, tab as delimiter doesn't matter.



not-tested.

HTH

You guys are making it WAY too complicated. A single IF statement using regular expression can handle the "largest" group:

Your GroupIDs have a specific pattern, and a regular expression can handle that match.



This code has been tested.

I can explain the regular expression, but check the help file for full documentation:

"E([0-3][0-9][0-9]|40[0-5])"

The "E" should be obvious. Matches the letter "E"

([0-3][0-9][0-9] | 40[0-5])

The "|" is an "or" statement, so it's broken up in two parts.

First part:

[0-3][0-9][0-9]

Matches 3 numbers. First one between 0-3. Second between 0-9, third one between 0-9, effectively matching anything from 000 to 399.

If you have a mix of alphanumeric, you can do [0-9a-f] for hexidecimal, for example.

Second part:
40[0-5]

Matches another 3 number. First two being 40, last one from 0 to 5, matching 400 - 405.

Do note that my example matches E000 to E405. If you do not want to match E000, it'll be quicker to add a "IF" statement checking specifically for E000 than to modify the regular expression to exclude E000 out of the range.

You can match billions of IDs with regular expression and it wouldn't slow it down by much.