Mail Archives: geda-user/2018/07/12/10:24:53
On Wed, 11 Jul 2018, Edward Hennessy (ehennes+oss AT fastmail DOT com) [via
geda-user AT delorie DOT com] wrote:
> Older schematics and symbols in existing libraries contain 0 in the line
> width. Maintaining backward compatibility and a new definition of width
> 0 would be more difficult to implement.
We can get away with almost anything as long as we increase the file
format number and add the logic for dealing with older files. (That said,
I think it's a good idea to add as little such logic as possible.)
As far as I see, there are the following options:
- Increase the file format number and re-define the meaning of width zero
to mean "no line". Older files would be re-written to a specific,
non-zero, default width.
- Increase the file format number and add a new line style (e.g., -1) to
mean "no line". Lines with width zero are treated as before.
- Increase the file format number and allow a special value for the line
width (e.g., -1) which means "no line". Lines with width zero are treated
as before.
- Add special case logic which will hide a line of width zero if the
object is filled with fill style "solid".
What do you think?
On Thu, 12 Jul 2018, karl AT aspodata DOT se wrote:
> Wouldn't it be sufficient just publish any patches in the mailing list.
I can't speak for others, but I will consider patches on the mailing list
just like patches on Launchpad. Please make sure to prefix the subject
with [PATCH] so the mail can easily be found.
- Raw text -