Jean-Marc LASGOUTTES wrote: > The original code initialized the hardcoded colors, then overrode them > with the system colors as necessary, and finally read the prefs to set > the use colors. This means that everything could be overridden nicely. > After the initial backlash, I had to add a checkbox. However, by the > time I have the value of the checkbox, I am already reading the prefs > and it is too late to read the system colors. Are you still following > me? > > So the current philosophy is different, since it implies to read colors > normally, but override them with the OS colors on the fly (the color > change without restarting when os them is changed, BTW). This means in > practice that all these colors are not configurable in LyX anymore. One > possibility would be to have: > > system background: set by system or linen by default > > user background: inherited by default (transparent), can be changed by > user. This is the color of the main text inset owned by the buffer.
i think nobody is going to fight with you as far as the framework is concerned. we can return back to the original version, kill the checkbox, add the background options as you have written now and set linen as a default. does it make sense for you? > > the note was against blind removals. for both issues raised in my last mail > > (background & graphics background) i tried to put reasonable arguments. > > Agreed, What about tabular lines now. Does someone think they deserve to > be configurable (not the dotted ones, the plain ones)? what color do you propose? i like they can be less visible then foreground text, but we can join it with other color(s). pavel