Mail Archives: geda-help/2021/02/26/10:02:15
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
- Raw text -