> 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
Talisman does this as well, as at one time mystic modified messages to
make them a maximum of 80 columns, so to display ansi without it getting mangled
along the way we had to save ansis with a limit of 79 characters
wide (which caused a lot of cursor positioning sequences.)
When I say modified, I don't mean locally, if it was used as a hub, it
would mangle the ansis on messages that just passed through the system. I
don't know if that is still the case or not.
> 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?
Andrew
---
■ Talisman ■ Tiny's BBS II - http://www.tinysbbs.com
|
