Zugg Software :: View topic - [309B] Problem with secondary windows and status bar.

Posted: Mon Jul 20, 2009 10:08 pm

If a status bar is added to a secondary window, horizontal scrolling is forced on the window. That means that word wrapping is effectively disabled. Windows with no status bars wrap normally. There shouldn't be a connection between the status display and the contents of the window. Note that scrolling is force even is there isn't an actual status being displayed. All one needs to do is check the status box in the window setting for enable this behavior. Also, unchecking the box in the settings does not remove the scrollbar (restores word wrap). The main window does not exhibit this behavior.

Posted: Tue Jul 21, 2009 5:12 am

That has always been the case. The horizontal scrollbar is part of the status bar. If you move the mouse just to the left of the horizontal scroll bar until the mouse cursor changes into a resize cursor, you can click and drag the scrollbar to resize it to zero so that you don't see it anymore.

This is done to maximize the vertical space available for your MUD session, rather than having the status bar and horizontal scrollbar on separate lines.

This *IS* true in the main window too. The main window and the secondary windows use exactly the same code...there is no difference.

Posted: Tue Jul 21, 2009 8:13 am

I understand the use, however, my problem is that world wrap is being disabled. So I am forced to make a choice between having status displayed or keep scrolling back and forth to read the entire text on the window, especially when the status being displayed does not consume the entire horizontal space available. Also, if the status line is removed, the scroll bars remain so there is no way to ever get word wrap back, except by deleting and re-creating the window.

EDIT: While it is true that the horizontal scrollbar also appears on the main window when a status line is present, the difference is that word wrap to the main window is not impaired.

Posted: Tue Jul 21, 2009 8:22 am

Anaristos: I wonder if this is related to the crash dump I submitted on my post (about Access Violations). Word wrap effectively became disabled (though the status bar had nothing really to do with it, as it wrapped fine in my child windows without status bars).

Ultimately, because word wrap stopped working, I had to shut down CMUD and restart it. Currently, because of the crash affecting my daily play, I had to revert back to 3.08 and hope Zugg is able to figure it out for the 3.10 release.

Charneus

Posted: Tue Jul 21, 2009 4:57 pm

Please post a procedure for reproducing the problem with word-wrap getting disabled. I have not been able to reproduce any problem with that in 3.09.

Posted: Tue Jul 21, 2009 11:22 pm

I don't know of an "offline" procedure to reproduce this problem. However, this is how I determined that having a status line (and the corresponding horizontal scrollbar) disables word wrap. The secondary windows get their text from captures. Without the status bar (and scrollbar), text captured wraps normally when the line length exceeds the window width. With the status bar (and scrollbar) text does not wrap. One is forced to use the horizontal scrollbar to read the entire line.
On the surface this makes sense since the presence of the scrollbar indicates that there is no need for word wrapping. So the issue is not that the scrollbars (which I don't want) are disabling word wrap, is that with scrollbars there is no "need" for word wrap so it is effectively disabled. However this only happens with secondary windows. The main window (which also has a status bar and, therefore, a scrollbar) doesn't exhibit this behavior. Word wrap works for the main window.
I've tested this by simply having a secondary window with a status bar and one without. I send a very long line of text to both, the one without the status bar (and scrollbar) wraps, the one with the status bar doesn't. Further, since the line is also echoed to the main window (because it echoes everything coming from the command line), one can see that it is appropriately wrapped.
Since, as you pointed out, the behavior for all windows, main or otherwise, should be the same, then there must be a bug since the secondary windows are "mis-behaving".

Posted: Wed Jul 22, 2009 12:14 am

Posted: Wed Jul 22, 2009 2:47 am

Once you get an access violation, then memory is corrupted, so all sorts of things can go wrong at that point. You should normally use the Close Application button with an access violation unless you already know that the crash isn't going to effect anything. The definition of "access violation" is that the application just "accessed" memory that is no longer valid. If this was a "read" operation, then you are probably safe. If it was a "Write" operation, then all bets are off.

Now, in the testing of your access violations, I never got word wrap disabled here. But typically memory errors like this are very system dependent. But if you can find a crash that consistently turns off the word wrap, please post a link. You have many different posts with many different crashes, so I have no idea which one you are specifically referring to with the word wrap issue.

Posted: Wed Jul 22, 2009 3:03 am

You must my reply, Zugg. I don't have any crashes, I just have word wrap disabled.