 |
Guinn
Wizard
Joined: 03 Mar 2001
Posts: 1127
Location: London
|
 Posted: Tue May 01, 2007 4:27 pm
[1.31] Creating triggers at same time as class
|
from the command input
first, make a trigger normally
#TR {test1} {whatever}
then make it within a class
#class Test
#TR {test2} {whatever}
#class 0
Then look at the two triggers in the settings editor - test2 (because it was made inside a class) has none of the options ticked so it'll never fire. Normally (and with test1) it'll have 'Fire on newline' and 'Trigger on trigger' checked by default
It's pretty annoying, having just reimported all my settings to try and ensure I'm past any old pkg corruption to find out that half my triggers aren't firing |
|
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;) |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue May 01, 2007 5:20 pm
|
I cannot reproduce this in a blank session. I ran CMUD, closed the Session window and type:
| Code: |
#class Test
#TR {test2} {whatever}
#class 0 |
on the command line. I then opened the settings editor and selected the test2 trigger and clicked the More button, and the Trigge on Trigger and Fire on Newline options were both checked.
Edited: Hmm, this is even weirder. It doesn't seem to matter if the trigger is in a class or not. It seems that if the Package Editor is open when you create triggers on the command line, every *second* trigger that you create has the options messed up. I have no idea how this is happening (or how it's even possible). Anyone else with more information on this would be appreciated, but it's on the high priority bug list. |
|
|
|
|
|
|
|
|
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
|
|
