X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
Date: Fri, 26 Feb 2021 16:02:03 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "karl AT aspodata DOT se [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
Subject: Re: [geda-help] How to get element outline off-board
In-Reply-To: <20210226140333.7D5E78248737@turkos.aspodata.se>
Message-ID: <alpine.DEB.2.21.2102261538470.17675@nimbus>
References: <xnh7nchcyj DOT fsf AT envy DOT delorie DOT com> <4b1d3d85-7f93-9eac-c4eb-9f84f2a47e61 AT bitflipper DOT ca> <CAMw9acBn7xNo5jvrvS6Dof6JtYgOOLVKJwFFTu93S+CoPszjHw AT mail DOT gmail DOT com> <20210225212042 DOT 16269 DOT qmail AT stuge DOT se> <20210226140333 DOT 7D5E78248737 AT turkos DOT aspodata DOT se>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Hi Karl,

On Fri, 26 Feb 2021, karl AT aspodata DOT se [via geda-help AT delorie DOT com] wrote:
> if I want to use *schem to make schematics with currents and voltages 
> indicated with lines and arrows, for inclusion into some doc. or paper

what you want to be able to control here is *join* style, not cap style. 
There is no field for this in the schematic file format, and so far, I 
considered keeping the file format stable to be more important than 
introducing a fix for the arrow case.  Lepton (ab-)uses the line cap field 
for that purpose, which mixes up two distinct concepts and isn't an 
acceptable solution in my opinion.  Also, special-casing line width zero 
for filled objects kind of patches the issue here but introduces yet more 
inconsistencies.

> In reacent geda-gaf, a few things that was formerly allowed, now fails
> or gets annoying error reports. Unfortunately I don't seem to be able
> test old and new gschem i parallell (having both installed gives me
> segfaults, in /usr/bin and /usr/local/bin) makeing it hard for me to
> show this.

As I said before, gnetlist only reports errors for situations which are 
clearly broken or can't guarantee a consistent output, and warnings for 
situations which produce an output that most probably isn't what the user 
intended.  If you think a specific error or warning message doesn't fall 
in these categories, please let me know so I can look into the situation.

As for the port/power symbol warnings you asked about a while ago, these 
were added to new-style ("portname="/"netname=") port and power symbols as 
this allows catching common user errors which used to silently result in a 
broken netlist.  You can just continue to use old-style ("refdes="/"pin=") 
port and power symbols if this is an issue for you.

Roland