Hi Apam,

I have noticed that when viewing messages with ANSI in them, that the origin/tear lines for the message are the same colour of the last part of
the ansi.
Ie: if the ansi's last colour was yellow, then so is the tear/origin
line. etc...




\/orlon



--- MagickaBBS v0.12alpha (Linux/m68k)
* Origin: Vorlon Empire: <Sector 550> (21:1/195.1)

Hi Apam,

I have noticed that when viewing messages with ANSI in them, that the origin/tear lines for the message are the same colour of the last
part of the ansi. Ie: if the ansi's last colour was yellow, then so
is the tear/origin line. etc...

That's not really a bug, as the tear/origin line is a part of the message
(if there is no reset ansi code posted it's not reset). However, it
relates to Tiny wanting different colours for quotes, if I do that, I'll
also do different colours for tag/origin lines.

Andrew

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)

Quoting apam to vorlon <=-

However, it relates to Tiny wanting different colours for quotes, if I
do that, I'll also do different colours for tag/origin lines.

Yes please for both? ;)

Shawn

... It's only a hobby... Only a hobby... NO! IT'S MY LIFE!
--- Blue Wave/386
* Origin: A Tiny slice o pi (21:1/130.4)

Quoting apam to vorlon <=-

However, it relates to Tiny wanting different colours for quotes,
do that, I'll also do different colours for tag/origin lines.

Yes please for both? ;)

I've implemented it into the msglib branch. I went for bright cyan for
quotes and bright blue for tag/origin lines. I should make the colours configurable, but unsure of the best way to do that? Through bbs.ini
maybe?

You can see it in action on the fat sandwich (it works both in the
telnet/ssh and www readers)

Andrew

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)

is the tear/origin line. etc...

That's not really a bug, as the tear/origin line is a part of the message (if there is no reset ansi code posted it's not reset). However, it relates to Tiny wanting different colours for quotes, if I do that, I'll also do different colours for tag/origin lines.

Oh, It looks weird that's all.





\/orlon



--- MagickaBBS v0.12alpha (Linux/m68k)
* Origin: Vorlon Empire: <Sector 550> (21:1/195.1)

is the tear/origin line. etc...

That's not really a bug, as the tear/origin line is a part of the
(if there is no reset ansi code posted it's not reset). However, i relates to Tiny wanting different colours for quotes, if I do that
also do different colours for tag/origin lines.

Oh, It looks weird that's all.

It's fixed now, though not in the master branch :)

Andrew

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)

On 17-Dec-2018 20:15, apam wrote to Tiny <=-

I've implemented it into the msglib branch. I went for bright cyan for quotes and bright blue for tag/origin lines. I should make the colours configurable, but unsure of the best way to do that? Through bbs.ini maybe?

I'm guessing i9's going to be a system wide setting, so bbs.ini would be appropriate.


... "It appears to be a tagline of unknown origin." - Spock
--- MultiMail/Win
+ Origin: Bush Track BBS (@6)
* Origin: FTN-MNET Gateway (21:1/50)

Quoting apam to Tiny <=-

I've implemented it into the msglib branch. I went for bright cyan for quotes and bright blue for tag/origin lines. I should make the colours configurable, but unsure of the best way to do that? Through bbs.ini maybe?

I think either in bbs.ini or in the strings file? Whatever is easist.
We can adapt to either. :)

You can see it in action on the fat sandwich (it works both in the telnet/ssh and www readers)

Perfect! Exactly what I was going to ask next. ;)

Shawn

... Interchangable devices won`t.
--- Blue Wave/386
* Origin: A Tiny slice o pi (21:1/130.4)