Zugg Software :: View topic

Newbie Joined: 12 Jul 2010 Posts: 3

Ok I'm having several reoccuring problems with Cmud.

CmudPro 2.37
Windows 7 Ultimate

1)
I use a simple capture trigger to put narrates and tells into a separate window, and it works fine while on the same session. However, sometimes when I switch from one session to another (IE a different character setup) the separate (Communnications) window becomes the main - The window named RogueGuy dissapears and the main window is called Communications. I found a workaround, entailing going into the package editor and selecting the RogueGuy tab and clicking the "window is visable" box. WHY DID IT BECOME UNVISABLE IN THE FIRST PLACE? The Communication window is hijacking my freaking main window and jams it so it won't connect to the mud.

2)
I color certain names, #cw Badguy yellow so they show up. While the main window works correctly, the colors don't always work in the Communication window, and leave the colored name the same as the background color of the Comms window. Kinda the opposite of what I was going for, eh?

3) MOST IMPORTANTLY All of a sudden I log back on, it does the retarded window hijack thing and now my CLIENT alias's are being sent to the mud. For instance, I have an alias:

#alias - {#variable target %1}

This WAS WORKING like 45 min ago, so I could type "- dark" and the variable target would be set to dark. NOW The dumbass client is sending "- dark" TO THE MUD. I tried deleting the alias, disable/enabling, and a couple other things, but CMUD is sending ALL of the aliases intended for changing variables and such TO THE MUD.

I am seriously unhappy with CMUD so far, and have had to rebuild all of my aliases and triggers three times so far, due to Packages getting corrupted, and appearing empty in the editor, and various other things. Is there some setting I've gotten wrong? DOUBLE-YOU-TEE-EFFFF This thing is really making me angry, and I'm about to go back to a freebie Client, and try to get my money back.

Wanderer Joined: 02 Sep 2005 Posts: 85

1) You don't close session windows or force-switch window focus? (#WIN) ? Might be what is happening here
2) No idea here, not really used #CW
3) I believe - is also not recommended for aliases, or any special char for that matter, see discussion on alias names using numbers as first and/or only characters...
note: I believe there's also an issue with corrupted packages.. I'd have to search for the topic..

ending with I'm not really sure myself, I'm just going with first impressions and I haven't really been on 2.37 in a while.. so. *shrugs*

Wizard Joined: 22 Mar 2007 Posts: 2320

1) You will have to give a detailed step-by-step procedure for how you are switching sessions for us to understand exactly what is happening here.

2) Unless you use an ANSI trigger, the trigger will not capture the color, and thus will not send the color with the line to Communication window. Possibly the best solution is to use a #CW trigger within the Communication window itself, or in a module outside any window which both windows can access.

3) Ithilion is correct that using punctuation for aliases is not recommended, and can lead to problems. Since this is related to the window thing, I suspect that this is a problem of scoping. One window cannot see the variables, triggers, and aliases which are defined within another window. So the solution here is probably to fix issue 1), or to move your aliases and triggers. If you need aliases and triggers to be available to more than one window, they need to be defined in a module outside of any one window. If this doesn't help, you will need to give us a lot more details on what is happening, preferably a step-by-step procedure.

Wizard Joined: 22 Mar 2007 Posts: 2320

Thinking further about it, problem 1) is probably a problem in your layout file. First, check your settings to make sure the Lock Layout is turned off. Then close the session. In the Sessions window, hold down the Shift key, then click the session icon and Open Session Offline. this will open the session without trying to connect to the mud, and replacing your window layout with the default layout. Recreate the window layout you want. The new layout should be saved after this.