 |
diehard2k0
Beginner
Joined: 17 Aug 2008
Posts: 25
|
 Posted: Sun Aug 24, 2008 11:02 pm
bug with #waitfor
|
Just letting it be known about the bug with #waitfor Not really an issue or anything
When i do #waitfor and the timeout timer times out, but at the same time it times out, the string comes up, it causes that little Error popup to come up. I just tell it to continue application and it's fine. Just letting it known that the timeout and the string coming up at the same time causes an error. |
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Mon Aug 25, 2008 3:21 am
|
I couldn't quite replicate your problem, but I do find a clear bug with #WAITFOR. The optional 3rd and 4th arguements are not being handled correctly.
Procedure
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter at the command line
| Code: |
| #ALARM +5 {#SHOW abc};#WAITFOR abc 10000 {xyz} |
You will see it gives an error regarding an argument still on the stack.
4. Enter at the command line
| Code: |
| #ALARM +5 {#SHOW abc};#WAITFOR abc 10000 {xyz} {def} |
The same error is being reported. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Aug 25, 2008 4:59 pm
|
I've added Vijilante's bug to the bug list. I still wasn't able to reproduce the original problem, but my guess is that the timing needs to be exactly right to show the problem, which makes it hard to reproduce.
|
|
|
|
|
|
|
|
