Know bugs:
ROM BIOS scroll BUG.....
------------------------
The scroll routine CONDOR uses in the BIOS ROMs uses the attributes
of the upper left corner character to fill in for undefined character areas
on the screen. For this reason it is wise to have a LEFT MARGIN of
one SPACE character with no attributes set at all. This problem will only
occur when the text screen is scrolled, it usually shows up in BBS menus or
maybe after a TAGLINE. I haven't seen it mess up a ansi in a message body
because of it and it would be awful to insert the esc[0m to every vBBS message
line automatically, it would cause lot's of problems with Condor it would get
in it's buffer and Condor would think they were Condor commands! You would
only want to use this work around for ansi type BBS menus, please! Condor can
be made to work around lots of BBS diddling with the data by... X-SAVE the
graphic then MORPH it, then just go straight ASCII and it will display almost
ANYWHERE. AND if it won't display for what ever reason I'll make it more
flexible and hard to filter out.
Examples below show the work around for ROM BIOS scroll bug:
Example one, the proper way...
┌This space critical ( after the esc[0m )
[0m [1;44m┌───────────────────────────────────┐[0m
[0mAttribute?
What attribute?
Example two, leaving the left space margin out produces
a blue line where it's not expected.
[0m[1;44m┌───────────────────────────────────┐[0m
[0mAttribute?
What attribute?
-------------------------------------------------------------------------------
