Zugg Software :: View topic

Posted: Sat Aug 22, 2009 4:17 am

If you click anywhere outside the command line (such as the scrollbar on the main window) you must again click on the command line to be able to type anything. While it may be true that the command line is a different object from the main window, it is a functional part of it, and so focus should be restored to it immediately since it owns the keyboard.
Also, the session toolbar does not function properly if the focus was taken away by a secondary window. One must click on the main window to access the Settings Editor, for instance. What causes this is undertermined and it doesn't always happen.
Also, if data targeted for window A is captured (or generated by a script) while window B has focus, the output will go to window B. In all these situations the target window was explicitly declared either in the #CAP command, the #MXP <DEST "..."> command, or the scope of the script. Again, I am not sure why this happens, but the occurrences are consistent.

Apprentice Joined: 10 Apr 2009 Posts: 145

I've noticed this sometimes too.. But only sometimes.. Usually, clicking anywhere on the main window means the command line gets the focus.. But not always.. Confused

Posted: Sun Aug 23, 2009 6:13 pm

I think the issue with the session toolbar not working when another window has focus is a new problem related to my attempts to determine which toolbar should be enabled for shortcut keys. For example, if the mapper toolbar is enabled, then pressing Ctrl-F will activate Find in the Mapper. If the main session toolbar/menu is enabled, then Ctrl-F activates the Find Text. The tricks for determining which toolbar/menu is enabled now depends more on the focus, and I can see where this might cause problems with using the toolbar.

As far as the command line focus, if clicking the MUD session window does not focus the command line, then your layout is messed up and the command line is not docked to the window properly. Hold down the SHIFT key when clicking the Open Offline action to reset the toolbar docking layout.

Posted: Sun Aug 23, 2009 9:44 pm

Why does the layout get messed up so often? It seems like a high percentage of the posts get resolved with this override to re-create the layout.

Posted: Mon Aug 24, 2009 4:45 pm

Because if you accidentally drag the command line, when it re-docks, it docks to the bottom of the main application window instead of the bottom of the MUD session window. To force it to dock to the session window, you need to first double-click the title-bar of the session window to undock it, then drag the command line to the bottom of the floating session window, then double-click the title-bar of the session window again to re-dock it. Now the command line will be properly docked.

It's just simpler in most cases to tell people to hold down the shift key when connecting to their session to reset the layout back to the default.

So it's not that the layout file is getting "corrupted" or anything like that. It's just that the 3rd party window docking system gives priority to the main application window rather than the embedded session window when docking a toolbar to the bottom of an embedded window. And there is no way for me to change that.

Posted: Mon Aug 24, 2009 5:48 pm

I wonder if disabling the un-docking of the command line is an option. Is there anyone that uses that on purpose? I've never used it on purpose, it always happens inadvertently to me.

Apprentice Joined: 10 Apr 2009 Posts: 145

When the "clicking the window doesn't focus the command line" thing has happened to me before, just restarting cmud has cured it, didn't need to reset layout or anything..

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, there are people who use it on purpose.

Posted: Tue Aug 25, 2009 4:06 pm

I'm actually considering splitting the "Lock Layout" into two different options: Lock *Toolbars* and Lock Window Layout. And then I'll have the Lock Toolbars be disabled by default to prevent new users from accidentally moving their command line toolbar.