Zugg Software :: View topic

Posted: Tue Sep 11, 2007 1:11 am

Has anyone else noticed this. It seems the command line loses focus on occasion.

I'm not 100% sure but it seems when information is captured to a child window. I also have some text clean up triggers in those child windows so that might be a factor.

It's relatively minor but can become really annoying.

[Edit] I just checked. It definitely seems to be the #CAPTURE that's causing it.

Wizard Joined: 14 Aug 2004 Posts: 1269

Haven't noticed it and I have triggers that capture text to child windows.

[EDIT: Do you have command lines on your child windows? I don't.]

Adept Joined: 04 Feb 2005 Posts: 246

I've noticed the focus problem, but haven't yet noted that it has to do with #capture....

Enchanter Joined: 09 Sep 2007 Posts: 605

I have similar problem and reported it, Zugg add it to bug list. Not exactly as yours, and #CAPTURE works fine.

In my case the automapper spams with rooms descriptions in child window while I move in main and mapper follows me. While I try to figure out what cause this problem (it was introduced in 2.03), I found that clicking anywhere on mapper window (and giving it focus) results in all movement commands also start going to child window, not the main. The main windows still have its tab highlighted, but the command line becomes locked. It not only lost focus but exactly becomes locked (like enabled=false, in Windows terms). To regain the ability to type commands I must click on the child window' tab and then click back on the main window tab.

Posted: Tue Sep 11, 2007 5:24 pm

Yes, this is on the bug list, but I haven't figured out what causes it yet. I have a script that reproduces the problem most of the time, but I haven't gotten around to figuring out the cause yet.

Posted: Tue Sep 11, 2007 5:51 pm

Thanks Zugg... and I'm sure you know this but CMUD and CMUDPro both rock. Now I need to find an SSH server to use it.