>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote:
>> However, I do not understand the logic between the getLyXName()
>> behaviour.
Angus> Between the getLyXName() behaviour and what else? Do you mean
Angus> 'Behind' rather than 'Between'? Assuming that you do:
Indeed.
Angus> Branches can define arbitrary new colours as their background
Angus> colour. I believe that the same mechanism can also be used to
Angus> add arbitrary character colours also.
Angus> So, getFromLyXName is simply adding a new entry to the
Angus> map<name, #rrggbb> used to store these colours. What is so
Angus> confusing about that?
No, it adds a new entry which has a lyxname, but no x11 value or
anything:
void LColor::addColor(LColor::color c, string const & lyxname) const
{
ColorEntry ce = { c, "", "", "", lyxname.c_str() };
pimpl_->fill(ce);
}
So, while it says that it succeeded, any code that tries to translate
a broken color name will be given a brand new unusable color and never
be warned of this fact. This is rude.
JMarc
