Zugg Software :: View topic

Newbie Joined: 12 Oct 2009 Posts: 3

I've been a long time user of zMUD, but as my new computer is running under Windows 7, I have to upgrade to cMUD (2.37, 64 bit). I've been using it for roughly two weeks and have one big grievance that is keeping me from purchasing a copy.

I have dual monitors with cMUD maximized on the secondary monitor. When I attempt to open a second connection in cMUD, it opens (very small) on the primary monitor. It is hidden by default (not selected) - I have to go to Window -> 2 to activate the window. The input box for this new window, however, appears underneath the first window.

I cannot initially use any macros on the second window - if I click on it, or on the input box for the second window, and press a macro, the command is sent to the first window. I can move the input box and resize the new window, and that gives me the ability to use macros on the second window, but the changes are not saved when I close the second window and open a new one.

If I maximize the second window on my secondary monitor, I lose the File-Edit-View menu as well as the Sessions-Settings-Library menu. I am now unable to use Alt to access the Window menu and switch between windows. I frequently use multiple windows to test code changes, so the ability to do this is a necessity.

I can live with all the other differences between the two programs, mainly because they were just preferences that can be relearned. I need the above piece of functionality to work properly and I'm wondering if anyone here has had similar issues or knows enough about cMUD to help me get it working.

Posted: Tue Oct 13, 2009 4:55 pm

How *exactly* are you making a second connection? If you are selecting another Session from the Session toolbar or window, then the window layout for the second session might be corrupted.

Close CMUD, then open CMUD and hold down the SHIFT key and click the Open Offline action for the second session to reset the window layout and toolbar for it.

If you still have trouble, give us the exact step-by-step instructions for reproducing your issue.

Newbie Joined: 12 Oct 2009 Posts: 3

Sorry for the delay. My account was banned for posting a screenshot, so we'll have to rely on words here.

Here's what I did:
File -> Open Session, held down SHIFT and clicked Open Offline. The window opened maximized on the second monitor and in the background (ie, I had to go to Window -> 2 to bring it to the foreground). When the first window was active, only one input bar was visible. When the second window was active, two input boxes were visible, with the one belonging to the second window on top. When I closed the second window, an error popped up attempting to save some XML to the database. I sent in an error report, so you should have a copy of that.

Attempting to do File -> Open Session and then double clicking on the same icon (I use one generic session for the mud) repeats the behavior I mentioned previously.

Posted: Wed Oct 14, 2009 10:07 pm

Try this to fix it.

1) Close CMUD
2) Run CMUD
3) From the main Session selection window, select your FIRST session icon, then hold down SHIFT key and click Open Offline
3.5) Make sure a single command line is visible.
4) Select File/Exit to close CMUD
5) Run CMUD
6) From the main Session selection window, select the SECOND session icon, then hold down the SHIFT key and click Open Offline.
6.5) Make sure a single command line is visible.
7) Select File/Exit to close CMUD

This should reset the command line and layout for both sessions.

Now, to connect to both sessions, run CMUD, double-click the first session icon. Once the first session is running, then use File/Open Session and double-click the second session icon.

To save this 2-session layout as a "super session", select File/Save Session As. Give it a name. This will create a 3rd session icon that you can use in the future to open both sessions and connect to both at the same time. This will also keep your 2-session window layout separate from the layout used for each individual session.

You should also select the Edit Session action for each session icon in the main Session window and then click the Files/Packages tab and make sure each session has a unique settings and layout file name.

Newbie Joined: 12 Oct 2009 Posts: 3

My temporary license expired while I was in the process of testing this, so I'm no longer able to open cmud. I suppose that makes this discussion moot, now.

In my use of mud clients I prefer to have one session per mud. I use dozens of characters to test everything I code and I don't want a new session for each character. I don't want to use different package files for each characters - in fact, I want package files to extend across sessions. Whether I connect to the test copy of the mud on windows or the test copy on the linux box, I want the same macros and triggers and map data I use on the live copy. I preferred zmud's behavior where I could open a new window at any time and have it layered on top of the other window.

For the time being I'll stick with running zmud on XP. I'm willing to try cmud again in the future, but I can't switch right now.

Posted: Thu Oct 22, 2009 12:08 am

Well, you can do that in CMUD too. The way packages work is completely flexible. You can put multiple windows within a single session and go into the Settings Editor and set the network connection for each window. Then create auto login triggers for each window. You can have shared packages between different characters. The Packages tab for your session gives you full control over what packages are loaded.

If you just want to open another connection without opening a whole new session, use the drop-down menu for the Session icon in the toolbar, then select the "New Connection Window" submenu, and then you will see a list of all your defined host/port connections. This will open a window without creating a whole new session.

The process used in zMUD is the same as creating a new window within CMUD (using #WINDOW, etc) and then setting it's network connection (or using #CONNECT).

Maybe you'll try it again in the future. The downside of greater flexibility is that it has a greater learning curve and can take time to figure things out. *Most* CMUD users wanted additional flexibility so that they could have *some* shared scripts, but also some separate scripts. For example, if you play a "fighter" and a "priest", then the MUD-specific scripts (like Paths, etc) might be shared, but some aliases and triggers would be different to handle the two different character classes.

The 3.x Beta version allows multiple character windows to share the same map window. Actually, zMUD didn't do this...it would open the same map for multiple characters, but you'd have multiple map windows taking up a lot more memory. The 3.x version lets you share a single map with multiple windows/characters and also set up different "Location" markers in case your characters are in different MUD rooms.