Zugg Software :: View topic - [314B - 316B] A somewhat annoying development with the Editor.

Posted: Tue Mar 30, 2010 1:24 am

Since 314B, if one has the Editor open and there is some interaction (which I haven't yet determined, but I suspect is the settings autosave) the Editor pane disappears and has to be re-acquired. It is annoying because it can happen right in the middle of typing. I recall this problem existed in 214 or thereabouts, then went away, now it is back.

Posted: Tue Mar 30, 2010 4:42 pm

You will need to give me an exact procedure to reproduce this. I am not seeing anything like what you describe happening here.

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

I've had problems in the 3.14b editor too. Things like not being able to paste with ctrl+v (happens sometimes and then you have to use the rightclick menu - solves itself when restating cmud) and not being able to register certain macro keys by pressing them but having to write the keyname instead. I just upgraded to 3.16b a few minutes ago so not sure if these bugs are still around though.

EDIT: I also suggest not using ESC for closing window but that's just my preference - I do it several times a day but never intentionally...

Posted: Thu Apr 01, 2010 12:42 am

OK, This problem is not confined to the Editor. If, for instance, you have the drop down menu open in the Mapper window and the MUD updates (text from the MUD comes into) the main window, the focus is lost and the menu is closed. This will happen each instance, so it is easier to test than with the Editor. This could also happen if secondary windows are updated from captures, but I really haven't noticed that.

Posted: Thu Apr 01, 2010 1:02 am

I managed to reproduce this by enabling the Automatically bring to front window with activity option found under User Interface/Window options section of the preferences menu. After disabling this option, drop down menus don't seem to close so maybe that is a solution you can use for now.

Posted: Thu Apr 01, 2010 1:22 am

Yes, that option might cause the problem.

When "Automatically bring window to front" option is enabled and the window receives text, it gets brought to the front of the user interface. This causes Windows to give it the keyboard focus. The recent 3.16 version "fixed" this by then giving the current command line the focus back. So maybe this is causing a problem when you have a menu open.

Let me know if that really seems like the cause and I'll look into it a bit more. I'm still looking for an exact step-by-step procedure for this please.

Posted: Thu Apr 01, 2010 1:33 am

1 open a session
2 create a second window for that session I used a capture window for the test called GroupTells
3 enable the automatically bring to front option for the second window (GroupTells in my case)
4 open mapper or settings editor
5 type #wait 5000;GroupTells:#show test (in the main session window command line)
6 open a drop down menu in the mapper or editor before #show test fires and you should see what he's taking about.

ps: thanks for adding mouse wheel scroll to script debugger.

Posted: Fri Apr 09, 2010 2:03 am

Here is a new development related to the Editor window being opened: If you press a keypad key for a direction (2,4,6,8 in my mud), the corresponding value will appear in the command line as if they NUMLOCK were off. If one closes the Editor window, the problem disappears. Unfortunately, like the lost of focus which I stated at the beginning of this post, it doesn't always happen and I have no way atm to determine what triggers the problem. However, it does happen often enough to be a problem since this will become part of whatever you type in the command line and you are not expecting the extra characters.