 |
Malach
Apprentice
Joined: 03 Nov 2007
Posts: 132
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
 Posted: Mon Nov 05, 2007 5:31 pm
|
I cannot reproduce this. Here is what I did:
| Code: |
TestList={a|b|c}
#TRIGGER (%numitems(@TestList) > 0) {#SHOW fired}
#ADDITEM TestList d
-> shows "fired" |
Note that the name of the function is %numitems with an s at the end. But I'm not getting any bounds errors. So it probably depends upon the exact contents of your string list, and how you are modifying it. So you'll need to show some more details. |
|
|
|
|
Malach
Apprentice
Joined: 03 Nov 2007
Posts: 132
|
Posted: Mon Nov 05, 2007 5:57 pm
|
Yeah, I'm starting to think it's just the string lists in general that the problem is with. I'm having a lot of problems when I start modifying them rapidly. I'll have to do some clean testing without my system at some point to try to figure out what it is.
|
|
_________________
Intel Core2 Quad CPU @ 2.4 GHZ with Windows Vista Home Premium and 2 GB Ram |
 |
|
|
|
|
|
