color question

[^}LC}<SolJah*KF]

When you type a message in AA, your message comes in a color. Do you know the hex code for that color? I need this ASAP!

[wrtlprnft]

0xffff7f

[DDMJ]

0xffff88

[wrtlprnft]

no, 0xffff7f

[Jonathan]

0xffff7f indeed (now we're the majority)

[ed]

Durka's right. The colour he's after is 0xffff88.

[Jonathan]

Some evidence.

ePlayer.cpp:

Code: Select all

static void se_DisplayChatLocally( ePlayerNetID* p, const tString& say )
{
    // ...

    if ( p && !p->IsSilenced() )
    {
        //tColoredString say2( say );
        //say2.RemoveHex();
        tColoredString message;
        message << *p;
        message << tColoredString::ColorString(1,1,.5);
        message << ": " << say << '\n';

        con << message;
    }
}

// ...

// builds a colored chat string
static tColoredString se_BuildChatString( ePlayerNetID const * sender, tString const & message )
{
    tColoredString console;
    console << *sender;
    console << tColoredString::ColorString(1,1,.5) << ": ";
    se_AppendChat( console, message );

    return console;
}

// Build a colored /team message
static tColoredString se_BuildChatString( eTeam const *team, ePlayerNetID const *sender, tString const &message )
{
    tColoredString console;
    console << *sender;

    if (sender->CurrentTeam() == team) {
        // foo --> Teammates: some message here
        console << tColoredString::ColorString(1,1,.5) << " --> ";
        console << tColoredString::ColorString(team->R(),team->G(),team->B()) << "Teammates";
    }
    else {
        // foo (Red Team) --> Blue Team: some message here
        eTeam *senderTeam = sender->CurrentTeam();
        console << tColoredString::ColorString(1,1,.5) << " (";
        console << tColoredString::ColorString(senderTeam->R(),senderTeam->G(),senderTeam->B()) << senderTeam->Name();
        console << tColoredString::ColorString(1,1,.5) << ") --> ";
        console << tColoredString::ColorString(team->R(),team->G(),team->B()) << team->Name();
    }

    console << tColoredString::ColorString(1,1,.5) << ": ";
    se_AppendChat( console, message );

    return console;
}

// builds a colored chat /msg string
static tColoredString se_BuildChatString( ePlayerNetID const * sender, ePlayerNetID const * receiver, tString const & message )
{
    tColoredString console;
    console << *sender;
    console << tColoredString::ColorString(1,1,.5) << " --> ";
    console << *receiver;
    console << tColoredString::ColorString(1,1,.5) << ": ";
    se_AppendChat( console, message );

    return console;
}

Note the (1,1,.5) all over the place.

tString.h:

Code: Select all

//! proxy class for inserting color markings
struct tColoredStringProxy
{
    REAL r_, g_, b_;

    tColoredStringProxy( REAL r, REAL g, REAL b )
            : r_(r), g_(g), b_(b)
    {}
};

//!< strings that know about color markings
class tColoredString: public tString
{
public:
    // ...

    //! Creates a color string inserter
    inline static tColoredStringProxy ColorString( REAL r,REAL g,REAL b )
    {
        return tColoredStringProxy( r, g, b );
    }
};

Let's see what happens when a tColoredStringProxy is appended.

tString.cpp:

Code: Select all

static int RTC(REAL x){
    int ret=int(x*255);
    if (ret<0)
        ret=0;
    if (ret>255)
        ret=255;
    return ret;
}

static char hex_array[]="0123456789abcdef";

static char int_to_hex(int i){
    if (i<0 || i >15)
        return 'Q';
    else
        return hex_array[i];
}

tColoredString & operator <<(tColoredString &s, const tColoredStringProxy &colorCode )
{
    if (st_colorStrings)
    {
        char cs[9];
        cs[0]='0';
        cs[1]='x';

        int RGB[3];
        RGB[0]=RTC(colorCode.r_);
        RGB[1]=RTC(colorCode.g_);
        RGB[2]=RTC(colorCode.b_);

        for(int i=0;i<3;i++){
            int lp=RGB[i]%16;
            int hp=(RGB[i]-lp)/16;
            cs[2+2*i]=int_to_hex(hp);
            cs[2+2*i+1]=int_to_hex(lp);
        }
        cs[8]=0;

        s << cs;
    }

    return s;
}

FYI, int(x*255) rounds down (at least for the range we're considering), so it's 0xffff7f, not 0xffff80, let alone 0xffff88.

[Lucifer]

Jonathan's basically declaring himself right and using code to support it. I'd suggest using a color picker app if you don't want to believe jonathan.

[DDMJ]

I didn't see what wrlt's image showed. It didn't load correctly for me. It looked like .

There's not much of a difference between the 2 colors. Here's a screenshot:

[Jonathan]

If it's so hard to see, why did someone claim it's exactly ffff88 with absolute certainty (i.e. claim the real value is wrong)?

BTW, I took a similar screenshot which also captures the graininess of the grid quite well. I fixed that in the version I had on my broken HD. Would it seem like a good idea if I fix it again (=place vertices closer to the viewpoint so the GPU doesn't run out of precision so soon) and try multitexturing as well, and publish it this time?

Edit: uploaded aforementioned screenshot.

[Z-Man]

Additional vertices? Sure, why not?

[^}LC}<SolJah*KF]

So it's declared. 0xffff7f and 0xffff88.

They are both the same.

[ed]

nah, they're not the same.
Me, I thought it was a stupid question, like "what number am I thinking of?".
Turns out the question was fine, it was me who was stupid.

Trying to unravel what jonathon posted from a non programmers point of view:
ColorString(1,1,.5)
int_to_hex(int i)
would make decimal: 255 255 127
converted to hex would be FF FF 7F

although ffff88 looks the same, it's not.

[Jonathan]

ffff7f is/looks similar but not identical to ffff88. Even 16-bit mode (5-bit blue) shouldn't change that if rounding isn't totally broken.

Unraveling: for each number passed to ColorString, multiply with 255, round down, clamp to 0≤x≤255 (in case input isn't in that range), and print as two hex digits.

[wrtlprnft]

Actually I wasn't even doing any calculations, I just hacked arma to display all color codes