• Re: 132x36 mode questions

    From g00r00@1:129/215 to Black Panther on Mon Nov 16 17:27:46 2020
    If you have a display file that is not saved at unlimited line length then youwill have this issue, so that is my guess as to why you are seeing this. Linesare counted by linefeeds saved in the actual file, if you don't save theANSI with unlimited line length (ie ANSImation, etc) then it will notaccurately pause during display.

    Can the pause prompt still be changed with the <pipe>RP## control code? That might be an option.

    You can do that but I don't think it would fix anything. If you want the screen to pause in a scrolling ANSI it just needs to be saved with unlimited line length (0 in Mystic's ANSI editor) so each line in the actual ANSI file is one line as displayed. If the cursor is moving around via location codes or auto wrapping, then the line count won't be accurate.

    I could probably improve on this in the future, its just worked this way for 20+ years.

    I think most people turn pausing off for scrolling ANSIs and/or use baud rate emulation and in the few cases where the pause is desired it just has to be saved a certain way.

    I'll make a note of it in the TODO to look at changing the logic.

    --- Mystic BBS v1.12 A47 2020/11/06 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)