Zugg Software :: View topic

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

I have just upgraded to 1.25

I have two separate windows apart from my main window which I use to throw stuff into I don't want to see in my main one. Now my problem is that when I log on now CMUD for some reason makes one of those other secondary windows my active window. So it throws all output from mud there and I have no idea how to make it stop.

Posted: Sun Mar 04, 2007 8:56 pm

Your session layout is messed up from a previous version. From the Sessions window, hold down the Shift key and click the Offline action. That will open your session without loading any layout file. Now move your windows around the way you want them. Make sure the other windows do not have any command line. Select each of the "child" windows in the settings editor and make sure the "No Network connection" option is selected.

When you exit CMUD, it will save your new session layout and the next time you load it, the window with the command line and network connection should get the output from the mud properly.

Note that there is a known problem with the #window command not working with the windows marked with No Network connection. I'll try to fix this as soon as I can, but I can't promise any time scale right now.

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

Solved it somehow but have no idea what went wrong. Was not funny to see all text from mud appear in a secondary window.

Anyone else seen this behavior?

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

Doesn't work, Zugg. It happened again now. Tried to upgrade to 1.26 but no change. Tried what you said there, but everything looks right. It's just that the output from the mud is put in the same window. The command line is on the main window and when I type a command the command itself is written in the main window while the mud output is in the secondary window...

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

Ok, fixed it again. It seems to be because of other problems that came with 1.25. I won't rule out that some of my scripts which is in some way not working any more may be causing it so don't lie awake over it for now.