 |
harley
Apprentice
Joined: 05 Apr 2008
Posts: 121
|
 Posted: Mon Mar 16, 2009 8:00 pm
%ismember [3.05]
|
Unsure why but All of my trigs using %ismember are now broke
| Code: |
#if {%ismember ( %1, @Variable) {#say Yes} {#say No}}
|
It doesnt work anymore. :( |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Mon Mar 16, 2009 8:41 pm
|
You have the wrong syntax.
| Quote: |
| #if (%ismember( %1, @Variable)) {#say Yes} {#say No} |
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Mar 17, 2009 12:54 am
|
This is going to be true of all your #if commands, not just the %ismember ones. The proper syntax is #if (expression) {true-command} {false-command}, which you'll find in the help.
|
|
|
|
|
harley
Apprentice
Joined: 05 Apr 2008
Posts: 121
|
Posted: Tue Mar 17, 2009 1:40 am
|
It seems i got a lot of work ahead of me.
It worked before so i just assumed that the newest update broke it
I will get to fixing, thanks guys. |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Mar 17, 2009 5:30 am
|
You could try using a text-editor with a complex regex-based find and replace, exporting your settings to XML, running a find and replace on the contents, and then reloading the new XML. But that's going to be a pretty advanced process because it's going to involve bracket-matching.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Mar 17, 2009 4:51 pm
|
If you run the Compatibility Report in the settings editor, it should find all of those errors for you.
|
|
|
|
|
|
|
|
