I have enabled the MUSHclient option of automaticaly reloading my script apon changes to the sript file. Good feature btw. Anyways, if you have errors in your script code then MUSHclient will tell you. Now, like any super-intelligent person, my memory is really bad. So I dont close the errors. Instead, I switch over to my script file and begin repairs. Once complete I save the file. Now heres the problem, MUSHclient is still in some kind of "error state" and now mush wont respond to many command keyboard commands and wont recognize a script file. Anyways, so like a super-intelligent person I close MUSHclient.. After this happening a few times I notice my computer is acting funny so I open up the process manager... oh oh... we've got like 6 ghost mushclient.exe's eatting up memory.
Any thoughts/comments Nick?
-RL
Yes, I have a bad memory too. ;)
I have noticed the occasional "ghost" MUSHclient, and have never really worked out what causes it.
Perhaps, as a workaround, copy the error message from the script window (click the Copy Details button) and paste it into a notepad window or something, and then close the error window promptly. :)
The only problem with that, is I generaly have around 10 errors, so copying them is really annoying.
Perhaps rather than a message window popping up you could apply a world option that would allow them to be sent to the muds output.
There are other options too that I'm sure you're aware of but the single-error-popup can be quite the annoyance.
-RL
P.S. When are you going to build 3.72?
When you say 10 errors, you mean for one problem? PHP seems to be the only script language that does that. The others raise a single dialog per script problem.
I am reluctant to do away with the dialog box, because otherwise scripts would pretty-much "silently fail". Sending an error to a window that might be behind everything else would not really be noticed.
I should be doing 3.72 in the next few days.