Zugg Software :: View topic

Wizard Joined: 14 Oct 2000 Posts: 1368

1. Start cMUD.
2. Connect to a new MUD.
3. Create a trigger to capture text to a window:
#trigger {ooc:} {#cap ooc}
4. Let it capture some text so it opens.
5. Assumption: MudNameWindow and oocWindow are windows that belong to the same session.
6. Click the ooc window so it is highlighted.
7. File->Close Session
8. The session it not closed, but the ooc window is. Is this really correct? From the assumption the session ought to have been closed, not just that single window.

A small extra notice:
1. Connect to the MUD again.
2. Send something to the ooc channel so the ooc-window re-opens.
3. Open trigger editor.
4. Notice how a duplicate ooc-window has been created in the settings.

Posted: Thu May 01, 2008 5:13 pm

Actually, the problem is that the Menu item is mis-labelled. It shouldn't really say "Close Session". It should just say "Close". For child windows it just closes the window. Only when you close the primary window for a session doesn't actually close the entire session. I agree that this is a bit weird. In zMUD, this was called "Close window" instead of "Close session", but it worked the same way.

But you are correct about the second bug. It's not just closing the window (like clicking the X for the window), it's getting rid of the object internally even though it's still in the settings, so #capture can't find it anymore. Definitely a problem and I'll add it to the bug list.

Although honestly, you reported all of these problems at the last second on release day, so chances of getting this stuff fixed for the release today is rather small.