 |
alluran
Adept
Joined: 14 Sep 2005
Posts: 223
Location: Sydney, Australia
|
 Posted: Thu Jun 02, 2011 1:32 pm
Change in Behavior for Command Input triggers | Bug in Command Input Triggers ?
|
In the past, I had the following regex trigger:
| Code: |
<trigger type="Command Input">
<pattern>$</pattern>
<value>#if (@Paging) {
Code Goes Here
#noinput
}</value>
</trigger> |
Which allowed me to press enter on an empty line and move onto the next page of results. It would ONLY fire if I pressed enter, and wouldn't interfere with other macros (e.g. F1-F12 bound to actions)
With CMUD Pro 3.34 however, If I press F1-F12 while this trigger is running, it captures my macro keystroke and blocks the input :(
Anyone know of a way around this? |
|
_________________
The Drake Forestseer |
 |
|
|
Fizgar
Magician
Joined: 07 Feb 2002
Posts: 333
Location: Central Virginia
|
Posted: Fri Jun 03, 2011 2:45 am
|
Switching from a regex to normal CMUD trigger should allow the trigger to only fire when pressing enter. However even with @Paging set to > 0 , it seems the enter command is still being sent to the MUD ignoring the #NOINPUT command in your #IF. Not sure what to suggest about that at the moment.
|
|
_________________
Windows Vista Home Premium SP2 32-bit
AMD Athlon Dual Core 4400+ 2.31 GHz
3 GB RAM
CMUD 3.34 |
|
|
|
|
|
|
