Infocard XML coding

Moonhead

Huor wrote:
http://www.asciizeichen.de/RGB.html for the first 6 numbers after 0x, guess the last are used for bold, normal and italic but dont know the code

Thanx!! Will it work wth hex (0x) values, or will I have to recalculate them into decimals? Of well, I can find that out soon enough.

FriendlyFire

FLDev’ll generate the code for you, otherwise remember the data tag has to be of the format BGR (RGB in reverse order), so say #AAF289 bold becomes 0x89F2AA01. You can write them directly in hex provided you prepend them with 0x.

Moonhead

FriendlyFire wrote:
FLDev’ll generate the code for you, otherwise remember the data tag has to be of the format BGR (RGB in reverse order), so say #AAF289 bold becomes 0x89F2AA01. You can write them directly in hex provided you prepend them with 0x.

Thanks!! It now all makes sense to me

Alex.

A couple of years ago I wrote a script to validate all Discovery development infocards based on Adoxa’s description in #4.
Today I ran it against our server-side overrides in dsacesrv.cfg and it was upset about this in an infocard:
<tra color=“0x-524056832” italic=“default”>(notice the minus before the number and the extra digit)
FL seems to tolerate this instead of treating it as invalid XML, producing this:

Which seems to be the same if the minus and extra digit are removed.</tra>

adoxa

It’s not invalid XML, but it is an invalid unsigned number. Recall that hex numbers have one subtracted, so the conversion to 0 produces a value of -1, which is white.