![](templates/Classic/images/spacer.gif) |
Ceres Wanderer
Joined: 25 May 2006 Posts: 88
|
Posted: Mon Oct 23, 2006 7:28 pm
[1.11] #ALARM not set correctly from command line |
Just to clarify - I KNOW THIS IS A BETA.
1. Start CMUD
2. Hit escape to close the Sessions window
3. Create a new window named Test '#Win Test'
3. Enter '#alarm 2 {:test:#SHOW Lets see what happens}'
The result is that every 2 seconds ':test2' appears in the untitled window. |
|
Last edited by Ceres on Tue Oct 24, 2006 6:33 pm; edited 1 time in total |
|
|
![](templates/Classic/images/spacer.gif) |
Zugg MASTER
![](images/avatars/164475849040f41c23b22fe.gif)
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Oct 23, 2006 7:53 pm |
If you open the settings editor and look at the alarm trigger, you will see that somehow the script for the trigger has gotten set to ":test2". So it looks like a problem with the parser for the alarm creation. I've added this to the bug list.
This isn't an issue with #ALARM. It's an issue using the :window: syntax. This example also fails:
#trigger {whatever} {:test:#SHOW Lets see what happens} |
|
|
![](templates/Classic/images/spacer.gif) |
|
|