Hello All,

Anyone else on Linux having issues with the configuration menu redrawing
after exiting the text editor?

First note, my Putty window is much larger than what would pop up on Windows for "mystic -cfg".

Recreation: Networking > Edit Areafix Help (top and bottom status lines are
80 columns wide, however the blue background for the editor itself is
spanning the width of my putty window), scroll up and down a bit, then hit ESC and abort.

When it goes back to the opening config menu, it doesn't redraw properly and tries to span the width of my putty window.

This only began happening once the editor was added.

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 12/13/17, Accession said the following...

Hello All,

Anyone else on Linux having issues with the configuration menu redrawing after exiting the text editor?

First note, my Putty window is much larger than what would pop up on Windows for "mystic -cfg".

Recreation: Networking > Edit Areafix Help (top and bottom status lines are 80 columns wide, however the blue background for the editor itself is spanning the width of my putty window), scroll up and down a bit, then
hit ESC and abort.

Tried to replicate this but was unable to, using putty myself from my windows machine to the linux vm via ssh and seems to draw correctly from the steps above.

Cheers!
Pequito

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

First note, my Putty window is much larger than what would pop up on Windows for "mystic -cfg".

If I am understanding you correctly this is probably the issue. Mystic's text editor uses clear to end of line codes to reduce text writes where applicable. If you have a window larger than 80 columns you're going to see blue bleed to the edge.

I suppose I could make it not use a blue background and then it'd remain mostly unnoticeable, or send a command to resize the terminal window to 80x25, or
just stop using EOL.

I haven't tested what you've said yet BTW this is just off the top of my head.

--- Mystic BBS v1.12 A37 2017/12/13 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/13/17, Pequito said the following...

Tried to replicate this but was unable to, using putty myself from my windows machine to the linux vm via ssh and seems to draw correctly from the steps above.

And is your putty screen 80x25?

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 12/13/17, g00r00 said the following...

If I am understanding you correctly this is probably the issue.
Mystic's text editor uses clear to end of line codes to reduce text
writes where applicable. If you have a window larger than 80 columns you're going to see blue bleed to the edge.

Understood on reducing the workload.

However, it seems something was done on the original configuration where this doesn't happen. As I mentioned, it only happens when this new text editor is utilized.

I suppose I could make it not use a blue background and then it'd remain mostly unnoticeable, or send a command to resize the terminal window to 80x25, or just stop using EOL.

I haven't tested what you've said yet BTW this is just off the top of my head.

I suppose it's not a huge deal if it doesn't bother anyone else. However, I don't use my Putty screen solely for "mystic -cfg", and don't really want to change it up just for that either.

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 12/13/17, Accession said the following...

On 12/13/17, Pequito said the following...

Tried to replicate this but was unable to, using putty myself from my windows machine to the linux vm via ssh and seems to draw correctly f the steps above.

And is your putty screen 80x25?

80x24, maybe the only difference?

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

On 12/13/17, Pequito said the following...

And is your putty screen 80x25?

80x24, maybe the only difference?

No. The first thing I said in my original message was that my putty window is way bigger than 80x24 (160x48 to be exact).

You having 80x24 is why you're not seeing any issues. Try enlarging your
window to see what I mean.

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 12/14/17, Accession said the following...

On 12/13/17, Pequito said the following...

And is your putty screen 80x25?

80x24, maybe the only difference?

No. The first thing I said in my original message was that my putty
window is way bigger than 80x24 (160x48 to be exact).

You having 80x24 is why you're not seeing any issues. Try enlarging your window to see what I mean.

Here are my settings and the font I use is Source Code Pro {free font} but
with these settings its almost like having NR @ max settings and not full screen.

https://imgur.com/a/DpFNj

Maybe this will help with the size you been trying to work with, I chose the font cause it was the smoothest one I could find and also supports extended characters.

Tried what you mentioned with res and mystic -cfg shrunk the window back down to I think 80x25.

Cheers!
Pequito

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

On 12/14/17, Pequito said the following...

Here are my settings and the font I use is Source Code Pro {free font}
but with these settings its almost like having NR @ max settings and not full screen.

The point is, you're using 80x24. You won't see the issues I'm having because your screen size doesn't allow for any fill to end of line above 80 columns.

Maybe this will help with the size you been trying to work with, I chose the font cause it was the smoothest one I could find and also supports extended characters.

I don't want my putty window at 80x24, that is my reason for question.. Everything else in mystic -cfg has forced that screen size, and has worked
fine forever (even in my bigger putty window) until the text editor was added.

Tried what you mentioned with res and mystic -cfg shrunk the window back down to I think 80x25.

I'm fairly certain g00r00 already knows what it is, as he already explained to me exactly what, how, and why this is happening.

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

I'm fairly certain g00r00 already knows what it is, as he already explained to me exactly what, how, and why this is happening.

I took a look at it and to fill the entire screen without using ANSI is probably going to make the editor feel much more clunky. I am leaning
towards just changing the text background to black to "mask" the issue.

Maybe I'll try it each way and see.

--- Mystic BBS v1.12 A37 2017/12/13 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/14/17, g00r00 said the following...

I took a look at it and to fill the entire screen without using ANSI is probably going to make the editor feel much more clunky. I am leaning towards just changing the text background to black to "mask" the issue.

Maybe I'll try it each way and see.

Instead, it seems you have locked down mystic's original configuration to always be 80x24. If you just did that with the text editor as well, it would
be fine.

Nothing else in Mystic's configuration goes to the end of line (when you have more than 80 columns, to be specific). It only started happening when the
text editor was introduced. Then when I exit the editor, the cfgroot1.ans
then decides to stretch across the wider screen also.

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Instead, it seems you have locked down mystic's original configuration to always be 80x24. If you just did that with the text editor as well, it would be fine.

Its not really locked down, Its just that its drawing and removing text
boxes, not a text buffer of lines that require clearing to end of the line.

The same codes are used for the description at the bottom of the screen. If I were to change that to a blue background you'd see the same bleeding when browsing the pull-down menu.

The only way to "fix" this and keep efficiency in ANSI-BBS is by the illusion of using a black text background. To give you an idea of the difference in efficiency if were to change it to "box" it in:

To draw a 80x25 screen with a single 40 character line of text (we'll say 23 lines in this case because of a header and footer) it would have to send 1840 characters to draw the screen (80x23). The terminal then would have to interpret all of those 1840 characters and make 1840 screen updates.

The method it uses now takes 109 characters (40 for the text, 69 to clear the deadspace) and the terminal would only have to make 62 updates (40 for the
text and 23 to clear the deadspace).

As you can imagine 1840 characters transmission and 1840 screen updates vs 109 character transmission and 62 updates is a pretty significant deal and would likely greatly affect how responsive the editor feels while you're scrolling around.

ANSI-BBS just doesn't have capabilities that other VT emulations have, so there isn't a lot to work with to maximize both efficiency and compatibility. The physical terminal window size determines how much of the screen is filled (at least by column anyway).

--- Mystic BBS v1.12 A37 2017/12/15 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/15/17, g00r00 said the following...

Its not really locked down, Its just that its drawing and removing text boxes, not a text buffer of lines that require clearing to end of the line.

The same codes are used for the description at the bottom of the screen. If I were to change that to a blue background you'd see the same
bleeding when browsing the pull-down menu.

I see what you're saying.

The only way to "fix" this and keep efficiency in ANSI-BBS is by the illusion of using a black text background. To give you an idea of the difference in efficiency if were to change it to "box" it in:

I get that, however would changing to a black background on the text editor
fix the fact that the main config screen "cfgroot.ans" gets stretched to the width of my window after exiting the text editor?

It almost seems like the text editor is changing the display settings (ie: filling up the width of my window), and then not reverting back to 80x24 when exited and the config screen is re-displayed.

Side note, and I'd like to clear this up first:

The issues were not with Putty. I'm so used to using putty that I didn't realize at the time I was using the remote console app (vmrc) from VMWare.
This application doesn't seem to act like putty in a sense it's giving you a REAL console window. The only way to adjust screen size is by editing /etc/default/grub and setting the graphics there, like any normal tty
console. So I would assume this would also happen on a physical console on
your actual machine.

However, I setup a new putty session at 80x24, and obviously I don't see any
of this. So I started messing around a little more... I then setup another putty session at 160x48. This was interesting. When loading mystic -cfg the window size actually automatically changes to 80x24 - which is neat-o. Then when I exit the config it goes back to my defined window size.

With that said, I may just have to go back to putty and ssh for this machine
as well.

Regards,
Nick

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)