Zugg Software :: View topic - [3.12 pro]#CLOSE and #WINDOW from within other settings (menus and aliases)

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

I sent an error report on it (might be two, seemed like it maybe wasn't going through so I filled out and sent twice), but if I use #CLOSE and #WINDOW from the command line to open/close an existing window there are no problems. If I try to do the same via the below, the AV is apparently caused when the #WINDOW command tries to retrieve the window data:

The window and all settings contained

Posted: Mon Nov 30, 2009 6:07 pm

I was not able to get any error with your script, but you didn't really give a specific procedure. Here is what I did:

1) Opened CMUD, closed the Session window
2) Opened the Settings Editor
3) Copied the XML from the first code box above and pasted it into the tree view. This created the Mines window
4) Clicked on the Untitled window and copy/pasted the XML from the second code box to create the "playgame" alias
5) Closed the Settings Editor and selected the Mines window. Clicked the X button in the upper-right to close this window
6) In the Untitled window, I typed:
playgame Mines
and it properly opened the Mines tab.

So, please give me the modified procedure that shows the error.

Apprentice Joined: 23 Jun 2004 Posts: 105 Location: Poland

BTW when I have opened another window (just create it to send to it text like 'tells you') CTRL+Q returned me 14, but when I close this window, CTRL+Q shows 9 ;|
So looks like another Window placed floating in some point make cMUD slowest :(

Posted: Tue Dec 01, 2009 12:22 am

I do not see this on any of my computers. Here is what I did:

1) Run CMUD, close the Session window
2) Press Ctrl-Q. On my computer, the result is 4.3
3) On the command line, type "#WINDOW test" to create a test window
4) Press Ctrl-Q again. Now it says 3.9

In this case, it is faster because the main window has fewer lines to scroll when the Test window is docked to the top. So now, double-click on the Test window caption to undock it. Now press Ctrl-Q. Now my result is 4.6. This is only slightly slower because the Test window is floating over the main window and Windows needs to clip the text around the floating window, which makes the Windows screen update a bit slower.

But I'm certainly not getting the huge speed difference that you are, so try this in a blank session to make sure it's not a problem with your scripts.

Also, in the future be sure to give the *exact step-by-step procedure* for reproducing an issue. There are so many ways to do the same thing in CMUD that without the exact procedure, it's hard for me or anyone else to try and reproduce your problem.

Apprentice Joined: 23 Jun 2004 Posts: 105 Location: Poland

Hi!
Of cours! When I did the same what You (close Session window and use CTRL+Q on this 'untiled' window that starts with cMUD) the tests ware almost the same (~1).
But when I did the test inside a session, with scripts:
1) After load the Session use the CTRL+Q. I suppose that the first fire the trigger parse them or smth so the result was 10.9
2) Use once more time CTRL+Q and get 9.5
3) On the command line, type '#Window test'. The new Window is docked on the top. The CTRL+Q still shows 9.5
4) Undock the test Window and place it near he mapper. CTRL+Q shows 13.1

There isn't any scripts, that involves test Window etc. So it seems, that only appear the window floating on the screen can slower cMud
Best Regards
Yodous