Mail Archives: geda-user/2015/02/14/00:41:52
On Feb 13, 2015, at 11:46 AM, Kai-Martin Knaak <knaak AT iqo DOT uni-hannover DOT de> wrote:
> John Doty wrote:
>
>> On Feb 11, 2015, at 3:19 PM, Kai-Martin Knaak
>> <knaak AT iqo DOT uni-hannover DOT de> wrote:
>>
>>> A unambiguous sort of symbols on save would finally solve a still
>>> standing issue you may remember: gnetlist behaves differently depending
>>> on the order symbols were added.
I don’t think canonicalization is really a fix. It might even make it harder to figure out which symbol is in control.
>>
>> I agree this is an annoyance.
>
> It messes with components that are represented by more than one symbol.
> Consider an opamp which is represented by the usual triangle and a
> separate box for the power supply. The power supply symbol contains the
> footprint attribute.
> This is good style and recommended for clarity. It reduces the clutter but
> still shows all the pins.
>
Yes. I use your symbols for this. Thank you.
> The netlister looks only at the first symbol of a group when it determines
> the footprint.
By default, using the old API, yes. I started calling this the "attribute censorship bug” over five years ago. But censor-fix.scm changes this behavior. It compares all of the attribute values of a given name associated with the package, and complains of mismatches. A back end can also use (gnetlist:get-all-package-attributes) directly in geda-gaf 1.8 or later to see all of the values.
> If the power rectangle was placed after the triangle, the
> netlister thinks, acts like this is a component without a footprint. This
> frequently leads to confusion among students I teach the fundamentals of
> geda.
I wish the code from censor-fix.scm had made it into 1.8. I tried. When Bas Gieltjes coded (gnetlist:get-all-package-attributes) on the C side, I rewrote (gnetlist:get-package-attribute) as a Scheme wrapper around it, with the bug fixed. But some developers believed that some users could be depending on this bug, and rewrote the wrapper to reproduce it. That’s what wound up in 1.8. The part of the code that actually fixes the bug is in censor-fix.scm.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -