[LyX/master] Prevent branch background color from leaking out of the document

Jürgen Spitzmüller spitz at lyx.org
Fri Jan 22 10:12:49 UTC 2021


Am Freitag, dem 22.01.2021 um 11:02 +0100 schrieb Jean-Marc Lasgouttes:
> What I had in mind is that we save the name when there is one, and
> the hexcode when there is no name.
> 
> Example:
> * code: Color_background, name: "background", rgb: "linen"
> => saved: "background"
> 
> * code: Color_mathbg, name: "mathbg", rgb: "@background"
> => saved: "mathbg"
> [Bonus: this @background notation does not exist yet, but it would
> help 
> us a lot to have such reference to colors]
> 
> * code: <dynamic>, name: "", rgb "#00aaff"
> => saved: "#00aaff"
> [this what I would like.]

I understand, but I do not yet get the purpose.

> In this last case, the color definition (#rgb, linen, @othercolor, 
> whatever) would be saved at the place in the LyX file where the
> relevant color is needed, but no name would need to be saved,
> obviously.

But where do we need (and want) such static colors?

> My take is that the name is only needed for the colors of GUI
> elements 
> that can be set in the color preferences.

What about the colors set in document settings (branch background,
greyedouttext, box background, index labels)?

Note that (some of) these need to be semantic in order to support
different color schemes. Branch most particularly.

> It seems to me that there are things that one of us (or both) does
> not understand in the other's line of thought.

obviously.

Jürgen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20210122/affa1375/attachment.asc>


More information about the lyx-devel mailing list