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: | fluid |
---|---|
Location: | wickliffe, ohio |
Users: | 4 |
Nodes: | 10 (0 / 10) |
Uptime: | 255:06:11 |
Calls: | 51 |
Files: | 15,838 |
Messages: | 50,899 |