Zugg Software :: View topic - [1.26] Command line issues: disappearance and the cursor

Beginner Joined: 08 Nov 2006 Posts: 14

I wish I could tell you exactly the circumstances under which this happens, but, on multiple occasions, I've found myself to be missing a command line entirely, even when it is checked-on in the window options (by right clicking the display area). This usually seems to come up when creating a new session and/or attempting to load layout files.

Also, I've developed a pet peeve for the cursor not always returning to the command line after I click on other windows or scroll back. Could you perhaps add a feature that makes the cursor always return to the command line as a default position when CMUD is the primary window?

Thank you.

Posted: Tue Apr 03, 2007 2:14 pm

We don't want that. It was done earlier, but that gave a strange bug where you basically couldn't get the focus away from the command line. The only way to control it, would be based on updates and there are soo many window focus and update changes that it would be near unusable.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I'll think about this issue... I think there should be a scripting way to do the same thing.

Beginner Joined: 08 Nov 2006 Posts: 14

I'd like to give this a little bump to see if anyone can give me any info on the disappearance of the command line in it's entirety.

Posted: Fri Apr 13, 2007 6:45 am

There was one particular problem with disappearing command lines (and double command line) that Zugg was pretty sure he corrected in either 1.26 or the soon to be released 1.27. Once 1.27 is out review you situation and see if you still have the problem.

Posted: Fri Apr 13, 2007 5:27 pm

When the command line disappears, it's because you have loaded a corrupted layout file. In general, you should not be trying to manually load layout files yourself. If CMUD didn't create the XLY layout file for the exact window/package configuration that you are currently using, then loading a different layout file probably won't work and can cause the command line to disappear.

This is because each window in a package is given a unique identifier, and the command line toolbar is assigned to that identifier. So if you load a layout that has the command line assigned to a different window identifier (for a window that isn't part of your current session), then you won't get any command line.

v1.26 should be working correctly if you always let CMUD itself create the layout files and load them automatically. 1.27 fixes a couple of other issues related to editing the session properties, but it still isn't going to help if you load some other layout file. Also v1.27 has removed the Save Layout and Load Layout options from the menu to help avoid these kinds of problems. Those menu commands were left over from when CMUD didn't automatically save and load layouts and for debugging purposes and are not needed anymore.

Wizard Joined: 14 Aug 2004 Posts: 1269

Zugg, isn't the layout only saved automatically when you close a session? What happens if you get your layout all how you want it (and I imagine it would be possible to spend quite a lot of time doing this), and then either
(a) suffer a power cut / battery failure after a few hours of playing;
(b) suffer a crash or lookup in CMUD;
(c) a BSOD;
(d) some other kind of error that meant you didn't exit CMUD properly, thus saving the layout you spend ages tweaking?
Does this mean all your work is lost? Why not keep the Save Layout option, but just remove the Load Layout option?

Posted: Sat Apr 14, 2007 12:26 am

You can still use the:

#CMD SaveLayout

command to save a layout at any time. The main problem with the Save Layout dialog is that it allows you to select any filename to save to, instead of just saving to the current default layout file. And once you start playing with different filenames, than it's easy to get a messed up layout.

For example, if you Save your layout, and then add a new window to your package and later try to load the layout that you saved, it will be messed up because the new window in your package doesn't have a corresponding entry in the layout file.

So, since saving layouts in the middle of a session is a more advanced feature, I think those advanced users can just use the #CMD that is given above. Or, you can always customize your toolbar and add the Save Layout command back. It's still available...just not added to the menu by default.

Posted: Sat Apr 14, 2007 12:42 am

Perhaps a different Save Layout option would be better. The current one is more of a Save Layout As - I think Seb just meant an easy way to force the same kind of file update that'd happen when you closed the session, just in case the session was never closed after you spent ages working on your layout. I think it'd be a commonly-used feature (nobody hates losing work), especially for people who multiplay.

Posted: Sat Apr 14, 2007 2:03 am

I've added this feature to the #SAVE command in the next version. So it will save the current layout to the current file (in addition to forcing everything else to save, such as the INI file).

Wizard Joined: 14 Aug 2004 Posts: 1269