1. Forum
  2. FidoNet
  3. SYNC PROGRAMMING

  • Initial design of Terminal class

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 20:32:48 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6861

    That said, I'm happy to see the background-attribute of the current getkey(K_EDIT) is restored when the insert indicator is used, so that change (fix) is a good one.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 20:36:08 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6862

    If anything moves the cursor up and re-prints a line, it should only be doing so when the current text on the screen is assured to have been read, in which case the line counter should be zero. The other use case (for moving the cursor up) would be animations or sprites for "full screen" games/doors, where the line-counting/auto-pausing of scrolling text wouldn't be used anyway.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 20:53:54 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6864

    Having curattr being the current attribute was a similar experiment that didn't pan out either. I didn't bother creating a new property for that yet, though it's something that would be trivial to add... coming up with a good name is the hard part for that one.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:09:20 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6867

    In this case, I would wonder: in what situation is lastlinelen not the length of the line line printed? I suppose one were to print "something\r", it'd be wrong (until such time as a linefeed was sent, then it'd be correct), but the only known use case for the lastlinelen is for *not* counting initial blank lines after user input, so it was not a problem. If we change it so that lastlinelen was only updated upon an output LF, I think that'd be a backward compatible change to the implementation and keep the intent of the variable/property name. But I don't think there's any reason to pursue such a change as part of this MR.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:20:16 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6869

    I'm not sure what you're saying, but it seems like you're fine with how it is. The reason to change the JS property was simply to avoid someone trying to use it for something else and being frustrated that it doesn't do what they expect.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:21:22 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6870

    That demo seems to work on the master branch too, except that it prematurely auto-pauses on line 22. So yeah, your abstraction adds support for a new use case. :-)
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:31:08 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6871

    Yeah, it hasn't been a problem. But I also don't think anyone's used lastlinelen but me (in C++) and it's behaved how I expected where/when I've needed and used it so most likely nobody's had an opportunity to be frustrated with it. A simple use/test would likely show the property behaving as expected:
    ```
    print("test");
    print("last_line_length = " + console.last_line_length); // Prints 4, as advertised
    ```
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:53:24 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6876

    All implementations of Terminal::clearscreen() would need this, yeah?
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:56:24 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6877

    It seems the master branch doesn't do this clearing, but probably should have. --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 20:57:06 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6865

    In which case it doesn't matter since it will be cleared on user interaction.

    I've wanted to to a few animation things in the past with line counting enabled, but couldn't use the built-in pause support for (ie: Animate drawing boxes, cool transitions, etc).
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 20:59:56 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6866

    If you have a demo/test for it, sure, but it's never been on my feature radar: once a script (or display file) starts moving the cursor around, I expected the script to be in full control of any output and input (and not depend on SBBS auto-pausing).
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 21:08:34 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6867

    In this case, I would wonder: in what situation is lastlinelen not the length of the line line printed? I suppose one were to print "something\r", it'd be wrong (until such time as a linefeed was sent, then it'd be correct), but the only known use case for the lastlinelen is for *not* counting initial blank lines after user input, so it was not a problem. If we change it so that lastlinelen was only updated upon an output LF, I think that'd be a backward compatible change to the implementation and keep the intent of the variable/problem name. But I don't think there's any reason to pursue such a change as part of this MR.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:23:34 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6879

    Master does it in outchar as part of the fall-through from the FF case.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:25:10 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6881

    Yeah, I missed the one in the header, fixed now.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:28:20 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6882

    On the master branch, a direct call to clearscreen() e.g. from JS, for an ANSI terminal user, would not go through outcom() (and thus not hit any FF case):
    ```
    void sbbs_t::clearscreen(int term)
    {
    clear_hotspots();
    if (term & ANSI)
    putcom("\x1b[2J\x1b[H"); /* clear screen, home cursor */
    else if (term & PETSCII)
    outcom(PETSCII_CLEAR);
    else
    outcom(FF);
    row = 0;
    column = 0;
    lncntr = 0;
    }
    ```
    Probably a bug.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:31:20 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6883

    Yeah, no real way to guess at if anyone has tried using it and been frustrated.

    ```
    print("Test\r");
    print("last_line_length = " + console.last_line_length); // Prints 0, as advertised
    ```

    :smiley:
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:39:34 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6885

    Does console.clearscreen() not work? You said clearscreen example worked (unless you lucked out and the ;eval command exactly wrapped?)
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:40:44 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6886

    Aha!

    ```
    if (autopause)
    sbbs->CLS; // outchar(FF);
    else
    sbbs->clearscreen(sbbs->term_supports());
    ```
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Tue Mar 25 22:42:20 2025
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/506#note_6887

    So now console.clearscreen(false) needs to be fixed.
    --- SBBSecho 3.24-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)