I like the information reported to me regarding errors in scripts, and it allows me to find and fix things much more quickly than other clients. However, I have a lot of difficulty when I get errors while online and actively doing something or when I get stuck in a loop. The dialog is modal and gets in the way of me entering any commands into the game. Here are my suggestions for possible improvements:
1. A modeless dialog that doesn't take away the main window focus. This is important to allow me to try and correct the problem via commands entered into the game or the script engine.
2. Display multiple errors in a listbox or treeview format, allowing me to expand the details on any particular error at my own leisure. This helps with infinite loops or just with remembering multiple errors and allows me to go back and fix them all easily.
3. Some sort of loop detection, to prevent the infinite loop from locking me out of the client (or worse, spamming the hell out of my game and friends in it). Obviously, I'm not sure how easy or hard it would be to integrate this with the current code. I know zMUD added a popup that gave me the option of disabling triggers when a loop was detected, and it's been a real (virtual) life saver.
4. Allow us to log the errors directly in the output window, or a notepad window, and maybe to a log file. If it doesn't work, we'll see something wrong in the output window and know to look in the "errors" window for the cause of it.
Thanks for listening, and I look forward to any comments on this subject.
1. A modeless dialog that doesn't take away the main window focus. This is important to allow me to try and correct the problem via commands entered into the game or the script engine.
2. Display multiple errors in a listbox or treeview format, allowing me to expand the details on any particular error at my own leisure. This helps with infinite loops or just with remembering multiple errors and allows me to go back and fix them all easily.
3. Some sort of loop detection, to prevent the infinite loop from locking me out of the client (or worse, spamming the hell out of my game and friends in it). Obviously, I'm not sure how easy or hard it would be to integrate this with the current code. I know zMUD added a popup that gave me the option of disabling triggers when a loop was detected, and it's been a real (virtual) life saver.
4. Allow us to log the errors directly in the output window, or a notepad window, and maybe to a log file. If it doesn't work, we'll see something wrong in the output window and know to look in the "errors" window for the cause of it.
Thanks for listening, and I look forward to any comments on this subject.