• 132x36 Message Editor

    From Mandarax@21:1/156 to All on Thursday, November 10, 2022 22:39:42
    Just curious if anyone else gets the ansi file for the full screen editor to show the 132x36 sized file? The correct .ini
    is loaded when I set my session to that screen size, however, the background ansi file is absent. The file is in the text directory and named properly (still using the default ansi files for testing). Anyone else have this happen, or know the fix?

    Thanks!


    Insomnia City BBS SysOp
    Kalamazoo, MI USA
    bbs.farcasternet.org Telnet 23, SSH 2222

    ... No one knows what's next, but everybody does it.

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)
  • From Mandarax@21:1/156 to Mandarax on Thursday, November 10, 2022 22:48:46
    Actually, it looks like alot of the larger screen size setting doesn't seem
    to work. If I set my terminal to the larger size, login, and choose the
    normal message editor instead of the full screen that bugs as well.

    It does adjust itself to characters per line, but still scrolls the input at
    a 25 line screen size. So if I type a longer message it ends up not scrolling the screen properly. Is there a setting I have messed up, or is this an
    issue in general with Mystic?


    Insomnia City BBS SysOp
    Kalamazoo, MI USA
    bbs.farcasternet.org Telnet 23, SSH 2222

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)
  • From sPINOZa@21:1/116 to Mandarax on Friday, November 11, 2022 10:12:00
    Actually, it looks like alot of the larger screen size setting doesn't seem to work. If I set my terminal to the larger size, login, and
    choose the normal message editor instead of the full screen that bugs as well.
    ...
    It does adjust itself to characters per line, but still scrolls the
    input at a 25 line screen size. So if I type a longer message it ends

    I havent looked into other than "80x24 screen formats" yet but I changed some settings in the .ini file. So my question is:

    Did you change the [Coords] in the "msg_editor.ini" file (coord1 & 2) ?

    Gtx!
    spI!

    --- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
    * Origin: -.sNd!GARDEn.- (21:1/116)
  • From Mandarax@21:1/156 to sPINOZa on Friday, November 11, 2022 11:15:05
    Did you change the [Coords] in the "msg_editor.ini" file (coord1 & 2) ?

    The editor uses a different .ini file for each screen size. so msg_editor.c132x36.ini . Like mentioned, that loads and displays fine. It is the "background" ansi file that does not display at all and should be msg_editor.c132x36.ans Both of these stock files I did not modify before testing the larger screen size.


    Insomnia City BBS SysOp
    Kalamazoo, MI USA
    bbs.farcasternet.org Telnet 23, SSH 2222

    ... Redundant book title: DOS For Dummies

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)
  • From Mandarax@21:1/156 to sPINOZa on Friday, November 11, 2022 11:17:36
    choose the normal message editor instead of the full screen that bugs
    Did you change the [Coords] in the "msg_editor.ini" file (coord1 & 2) ?

    Also, if you were referring to the scrolling while adding lines of text, I was talking about the normal NON fullscreen editor. That doesn't use an .ini file for any configuring. Both the fullscreen editor and normal line editor do not seem to work like they should at 132x36.


    Insomnia City BBS SysOp
    Kalamazoo, MI USA
    bbs.farcasternet.org Telnet 23, SSH 2222

    ... The shortest distance between two points is under construction

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)
  • From osito@21:2/150 to Mandarax on Friday, November 11, 2022 17:33:12
    Yes, if you want to display pipe codes in an ansi with 137 columns(well with windows operating system anyway) you have to keep them within the 80 x 24 space, if they go outside, wierd things happen. blank spaces get added and locating the cursor in a desired location ends up completely somewhere else. i always assumed it was a bug in the compiling of the win 32 version.
    osito

    Osito

    --- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Mandarax@21:1/156 to osito on Friday, November 11, 2022 23:00:06
    Yes, if you want to display pipe codes in an ansi with 137 columns(well with windows operating system anyway) you have to keep them within the
    80 x 24 space, if they go outside, wierd things happen. blank spaces

    Well, my BBS is running on Linux and I'm working on it via Linux. So I am assuming its more than just Windows causing an issue ? I am having ansi and pipe files display on 137 columns on other menus and such fine. Just my Mystic for some reason does not display the msg_editor.c1... file at all when on that screen size. The editor itself works fine, and displays and positions the text from the msg_editor.c132x36.ini just fine. Like the To, Subject, Insert Mode, etc are all located correctly, just no surrounding ansi file to frame it all up.


    Insomnia City BBS SysOp
    Kalamazoo, MI USA
    bbs.farcasternet.org Telnet 23, SSH 2222

    ... You can learn many things from children... like how much patience you have

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)
  • From sPINOZa@21:1/116 to Mandarax on Saturday, November 12, 2022 13:02:58
    Also, if you were referring to the scrolling while adding lines of text,
    I was talking about the normal NON fullscreen editor. That doesn't use
    an .ini file for any configuring.

    Ok, I understand. As I said, I havent looked into this different screen formats yet but remembered I changed coordinates for my own system.

    Gtx!

    --- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
    * Origin: -.sNd!GARDEn.- (21:1/116)
  • From Mandarax@21:1/156 to Mandarax on Saturday, November 12, 2022 20:59:55
    Just curious if anyone else gets the ansi file for the full screen
    editor to show the 132x36 sized file? The correct .ini
    is loaded when I set my session to that screen size, however, the background ansi file is absent. The file is in the text directory and named properly (still using the default ansi files for testing). Anyone else have this happen, or know the fix?

    So, I've narrowed this problem down to Netrunner, and not Mystic (I am assuming). Utilizing Netrunner as my client most often the msg_editor ansi file would not load properly on a 132x36 size, but would sometimes. I then decided to give SyncTERM a trial at the wider screen size and it displays the ansi header frame every time. So something between Netrunner and Mystic is going wrong when loading that ANSI.


    Insomnia City BBS SysOp
    Kalamazoo, MI USA
    bbs.farcasternet.org Telnet 23, SSH 2222

    ... Press any key to continue or any other key to quit...

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)