X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Thu, 12 Jul 2018 16:23:41 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] adventures using arrows (for documentation), or
	cross my lines
In-Reply-To:	<20180712035814.AAF7E8420410@turkos.aspodata.se>
Message-ID:	<alpine.DEB.2.20.1807121608340.5988@nimbus>
References:	<20180702125528 DOT D32CF81F76FE AT turkos DOT aspodata DOT se> <20180709204944 DOT GA921 AT debian DOT lokolhoz> <20180712035814 DOT AAF7E8420410 AT turkos DOT aspodata DOT se>
User-Agent:	Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

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 -