Just checked the ansi and didn't see anything. It views fine for me using SyncTerm and Netrunner. Don't know what it could be.
Just checked the ansi and didn't see anything. It views fine for me using SyncTerm and Netrunner. Don't know what it could be.
@VIA: LUN
@MSGID: <62A4C196.16975.dove-ads@vert.synchro.net>
Just checked the ansi and didn't see anything. It views fine for me using SyncTerm and Netrunner. Don't know what it could be.
On 11 Jun 2022, Cozmo said the following...
@VIA: LUN
@MSGID: <62A4C196.16975.dove-ads@vert.synchro.net>
Just checked the ansi and didn't see anything. It views fine for me using SyncTerm and Netrunner. Don't know what it could be.
Mystic sees ANSI fine... I am under the impression that future builds of Synchronet will also see ANSI as well in the message base
@MSGID: <62A63B51.16985.dove-ads@vert.synchro.net>
@REPLY: <62A61B29.16983.dove-ads@vert.synchro.net>
@TZ: c1e0
Re: Re: Lunatics Unleashed
By: IB Joe to Cozmo on Sun Jun 12 2022 10:58 am
On 11 Jun 2022, Cozmo said the following...
@VIA: LUN
@MSGID: <62A4C196.16975.dove-ads@vert.synchro.net>
Just checked the ansi and didn't see anything. It views fine for m using SyncTerm and Netrunner. Don't know what it could be.
Mystic sees ANSI fine... I am under the impression that future builds o Synchronet will also see ANSI as well in the message base
Synchronet "sees ANSI" fine as well. What you're confused about is that Mystic will strip-out cursor-positioning sequences before displaying
ANSI in messages to its users. I made a change to do something similar
in my msglist.js module. I made no such change in Synchronet itself as that would make ANSImation in messages impossible. And most other BBS programs won't modify the ANSI before showing to a user either, so its best practice to just not include the cursor-positioning sequences in
the first place. --
This is how most BBS programs send ANSI-encoded messages. The only exceptions that I know of are Mystic and now Synchronet's msglist.js,
which will modify the ANSI contents, stripping away cursor-positioning sequences, before showing them to the user. The best solution is to
sequences, before showing them to the user. The best solution is to
not include the unintended cursor-positioning sequences in the message
in the first place. Using TheDraw, this can be achived by using the
"block save" (Alt-B) command.
sequences, before showing them to the user. The best solution is to
not include the unintended cursor-positioning sequences in the message
in the first place. Using TheDraw, this can be achived by using the "block save" (Alt-B) command.
That would be the best solution I suppose, but I wonder wouldn't messages with intended animation have the same effect as those with unintended
cursor positioning codes?
You're doing a great job!!!
Thanks. I guess I need to do a better job of explaining things however.
I did use it in the previous ansi's. But I had to change some of the text. So I had to resave it. I tried something someone suggested to me but I guess it didn't work.
Sysop: | Gary Ailes |
---|---|
Location: | Pittsburgh, PA |
Users: | 133 |
Nodes: | 5 (0 / 5) |
Uptime: | 113:34:40 |
Calls: | 735 |
Files: | 2,171 |
Messages: | 82,852 |