 |
Anaristos
Sorcerer
Joined: 17 Jul 2007
Posts: 821
Location: California
|
 Posted: Mon Jun 28, 2010 7:44 am
[321B] #CLOSE sends garbage to the mud.
|
I noticed that after a script used the #CLOSE command I would get the following on the screen:
| Code: |
Input too long. Truncating.
Unknown command. Please check the helpfiles.
|
So I decided to enter the command from the command line. What I saw was that after closing the window lines containing data from variables were being sent to the mud. I did nothing fancy just:
| Code: |
#CLOSE <windowname>
|
This happens consistently.
This is a brand new package. Built by hand one item at the time. |
|
_________________
Sic itur ad astra. |
 |
|
|
Anaristos
Sorcerer
Joined: 17 Jul 2007
Posts: 821
Location: California
|
Posted: Mon Jun 28, 2010 9:25 pm
|
It seems that this problem only occurs when using #CLOSE on windows created via #MXP.
|
|
_________________
Sic itur ad astra. |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Jun 29, 2010 4:49 pm
|
You'll need to give us the exact procedure to creating the window and reproducing this problem. Windows created via MXP (or other child windows) do not have any network connection, so I can't see how they could possibly be sending anything to the MUD unless you have some script doing this.
|
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Wed Jun 30, 2010 3:38 am
|
| Quote: |
Windows created via MXP (or other child windows) do not have any network connection, so I can't see how they could possibly be sending anything to the MUD unless you have some script doing this.
|
#WINDOW:
-->command line is unchecked
-->status bar is unchecked
-->visible is checked
-->docked (in tile mode, ie, like posts in a thread) to last window with focus (tile direction perhaps related to the last window docked to said window, ie, if you have two windows with the second docked above the first then #WINDOW thirdwindow = also docked above the first window?)
-->no network connection radio set
-->no packages checked for this window beyond its own
New Window button (Package Editor):
-->command line is checked
-->status bar is checked
-->visible is checked
-->tabs window to last window with focus (not sure if it's specifically the main window or not, but that was the last window with focus other than the package editor)
-->Override Network connection radio set (albeit, while enabled, the host/port boxes remained empty)
-->all packages checked for this window
#MAKEWINDOW (#MAKEWINDOW windowname, no options specified):
-->same as #WINDOW, but floating
#MXP <frame> tag (<frame name='ghi' width = '20c' height='10c'></frame>):
-->same as #MAKEWINDOW
-->interestingly, the SCROLLING argument is now on by default (is there an updated MXP documentation page I don't know about?)
-->nothing in the debugger is displayed on open or #close of the window except the usual horizontal bar and the comline start/stop messages. |
|
_________________
EDIT: I didn't like my old signature |
|
|
|
Anaristos
Sorcerer
Joined: 17 Jul 2007
Posts: 821
Location: California
|
Posted: Wed Jun 30, 2010 7:39 am
|
I posted a long time ago (pre 2.37) that MXP windows cannot turn off scrolling. The parameter is ignored.
As to the problem itself, I don't know what to say other than it happens. The MXP window is not trying to send text to the mud. But the #CLOSE command is entered in the main window context that is why it (the garbage) gets sent to the MUD, since the main window does have network access.
The procedure is nothing special, after I am done with the MXP window, the script issues a #CLOSE on the window. At that time, I get the messages I posted above, though I can't see what is being sent. However, if I manually enter the #CLOSE from the command line, I can see what is happening, namely, the contents of variables are being sent to the MUD. I will start running with the debugger on to see if I can capture the sequence. |
|
_________________
Sic itur ad astra. |
|
|
|
|
|
|
