 |
GeneralStonewall
Magician
Joined: 02 Feb 2004
Posts: 364
Location: USA
|
 Posted: Fri Mar 26, 2010 3:55 am
[3.14a] BUG? #Oninput prevents further processing on line.
|
I believe I remember something like this coming up before, but I couldn't find it. What's happening is I have a two triggers with identical trigger patterns. The first trigger (has a lower priority #) calls an oninput triggers, which fires. The problem is the second trigger never fires. If I reverse the priority numbers, then everything works fine. Here's the code to replicate, merely type #echo test and you should see what I mean.
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger name="test2" priority="11" copy="yes">
<pattern>test</pattern>
<value>#print {Test2 Fired!}</value>
</trigger>
<trigger type="Command Input" priority="30" copy="yes">
<pattern>oninput</pattern>
</trigger>
<trigger name="test1" priority="10" copy="yes">
<pattern>test</pattern>
<value>#print {Test1 Fired!}
#send {oninput}</value>
</trigger>
</cmud> |
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Mar 26, 2010 4:43 pm
|
Confirmed and added to bug list. Definitely a weird one.
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
