Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
Anaristos
Sorcerer


Joined: 17 Jul 2007
Posts: 821
Location: California

PostPosted: Thu Sep 17, 2009 3:44 am   

[310B] Odd behavior of #CLOSE
 
Beginning with this beta version, whenever I execute a #CLOSE command, the string "16" is sent to the MUD. At first I thought that the problem was with the scripts that used the command, however, this happens even when I type it from the command line.
The window is closed and the string '16' appears as a command sent to the MUD. This problem does not occur in a blank session but it is solid when working in a MUD session even if offline. The window can have been created with either #MXP or #MAKEWIN so that doesn't appear to be a factor. Also creating the window from the command line or script has the same result.
I've waited as long as I could before posting this problem, but I am stumped. So there you have it.
_________________
Sic itur ad astra.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Thu Sep 17, 2009 3:52 pm   
 
The #CLOSE command requires an argument. You either need to specify the file number to close, or the window name to close.
Reply with quote
Anaristos
Sorcerer


Joined: 17 Jul 2007
Posts: 821
Location: California

PostPosted: Fri Sep 18, 2009 3:23 am   
 
I am sorry if I gave the impression that I was using the command without an argument. I am specifying a window name, after the window closes the string "16" is sent to the mud. The string is not generated by a script since it is also output if the command is entered on the command line.
_________________
Sic itur ad astra.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Fri Sep 18, 2009 4:17 pm   
 
Something must be messed up with your session. I just did:

#WINDOW test
#CLOSE test

in one of my MUD sessions and it worked just fine.

You should run the Script Debugger and see if some scripts or events are running when you close the window that might be causing this behavior. For example, maybe you have something in the onExit event that is causing the output.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Page 1 of 1

 
Jump to:  
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

© 2009 Zugg Software. Hosted by Wolfpaw.net