Zugg Software :: View topic

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

First I'd like to start of by saying I use one settings file for all of my characters. Note, this does not mean one per character, but one global settings file. My problem being this:

1 ) Log on character Mumra. opens up a capture window named
"channels"
No problem, just the way i love it.

2) Log on second character. opens up the character window, and unfortunately it opens up a second capture window named "channels".

Is there a way I can have zMUD avoid opening another new child window
when one exists with that name already?

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Try

#if (%window(Channels) != 1) {#WINDOW Channels}
In other words, if the Channels window doesn't exist, make it.

Guinn

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

You don't get it. it isn't based on a trigger. it is based on saved windows.. if i was to use that trigger, and save my settings with the window open, it would also just do exactly what it is now..

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

Adept Joined: 20 Jul 2004 Posts: 268

I think he means like when he plays the 2 cahractes seperate he has #cap scripts for both.
But when he plays then together, if for Char1 there is a window called TELLS & for Char2 there's a window called TELLS, how can he have them merged so that there is just ONE window called TELLS.
At least that is my guess.
I have the same prob.
Had to actually turn off my #caps for the 2nd char cause the extra chat windows ticked me off, and everything was going into just one of the 2 chat windows any way

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

that's basically it, DeathDealer. I can do it with triggers, and have it work fine. my main problem is when i load a character, if it has a
'child' window saved in it settings, then when i open it it automatically opens the window, regardless of a trigger. sure, i could make a
trigger to close the extra window.. but i'm more curious if there is a way to just stop it from popping up in the first place.

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

DeathDealer, your problem is solely a layout file problem. You are connecting two characters in succession. If both characters are set to use a layout file, that means both characters will load up their assigned layout files and apparently the layout module doesn't check for the existence of common windows (this last part is probably a bug and should be reported if it hasn't already).

What you need to do is create a multi-character layout. An MCL will allow you to combine two layouts into one file, moreorless, and handles the connection of ALL the characters contained therein. See my previous post about how to create an MCL. As I said in that post, I dunno if it will change the layout behavior so if it does not you will have to stop using a layout for one character.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Talk about a necro thread! But it is my own thread. Anyway. The problem still persists.. and while MattLofton's solution would work if I was constantly logging the same two characters.. my experience is fluid. I have upwards of 40 different characters at max level. I use simple aliases to log them, it opens them up, etc. but the multiple child window thing is still an issue. Is there a way to make it so the default layout is NO child windows.. and no matter what.. that setting never changes? This would pretty much solve my issue I guess. Since one would only be opened on an actual captured trigger. The window just wouldn't open till then.

Novice Joined: 08 Dec 2005 Posts: 35 Location: Sweden

Make separate "sessions" for each window? That never get connected, but that you open a session on? Could have an alias to open it up, but you'd use #ses instead of #window.

Could also make a trigger on logging on to open up those sessions if they aren't already opened.