Hi Peter,
[snip]
> - "Overlay" screen colour map (what is this even used for?)
Where do you see this color map?
[snip]
> N.b. that the "colour override" feature would be disabled for the time being.
> What was the original motivation behind this feature, anyway?
End users would be able to override the color of all nets, pins,
buses, but I suspect it is not used at all and can probably be removed.
As long as there is a way of changing the color of these objects (nets,
pins, buses; when loaded/saved), then the override feature can be removed.
[snip]
>Feedback appreciated.
>
Seems reasonable. A couple of things that I would like preserved
from the existing colormap mechanisms:
- Setup of the color maps should still happen in the gschem-darkbg
or gschem-lightbg scheme files. Unless there really is a good
reason to move them elsewhere.
- The whole mechansim with the index of the color being stored in
the individual object definitions (in sch/sym files). I don't
see how we could change this without breaking everybody.
- The mapping of index to what the color is used for cannot be
changed. I.e. Color index 6 has to stay as logic bubble color.
I'm okay with disallowing the end user to change this mapping
(as you can today; but that's just silly as doing so would
break things).
- Ability to understand the color index mapping. Somehow the
end user should be able to figure out that color index 4 is the
net color or that 5 is the attribute attached color. If this
is just a comment in the *bg files, I'm okay with that too.
- It's "color" not "colour" <g> :->
-Ales
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
