Hello Digital,
On Thu Sep 19 2019 17:14:44, Digital Avatar wrote to Digital Avatar:
...aaaaand disregard. Fun fact for anyone else who runs into this
problem: the trimming and padding functions used in conjunction with
the MCI code system is *very* unforgiving. It expects exactly 2
digits. No more, and more importantly, no less. So if you do something like, say, pipe $R4 pipe &4, Mystic will happily give you the finger
and just print out the string '&4'. If, OTOH, you use pipe $R04 pipe
&4, you'll get the results you expect.
Yep, it takes some getting used to, and there still a couple head scratchers I've had to deal with recently. For example, if you decide to do a screen (23-24 line ansi at least) for last callers, in the process of using pipe codes
at the end of the ansi for starting cursor placement, then somewhere in the strings editing some of those to just go to the next line, it would end up giving a pause prompt after the first node was displayed, and after hitting enter, would show the rest of the nodes in the correct places. I believe all it
took to remove that pause prompt was to add a PO MCI code in one of the strings
(as it was already at the top of the ansi, but didn't seem to be doing it's job).
NOTE: Edited because Mystic dutifully converted the pipes into color codes. *sigh*
HAHA!
Regards,
Nick
... "Friends help you move. Real friends help you move bodies."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (46:1/100)