Re: gEDA-dev: get pin attribute by pinseq

[Ales Hvezda <ahvezda-at-NOSPAMseul_dot_org>]

Hi Stuart,

I have confirmed your observations.

>It raises the question:  How are slotted parts treated by gnetlist
>anyway?  In general, I believe gnetlist creates list of (pinnumber,
>attached_netname) pairs for each component.  But this seems to throw
>the slotting information away when this list is built.  Where is it
>created?  Perhaps in some libgeda function?

	The slotting information within libgeda/gschem/gnetlist is
really just used to assign the pin number to the associated pin
(identified via pinseq) of a particular instances of a slotted component.
That means that each slot of the instanciated component has the same
pinseq attributes (say 1,2,3) regardless of the slot number.

>Meanwhile, get_attribute_by_pinseq seems to work for slot 1, which
>means that pinseq info is somehow associated with the part (presumably
>as attributes attached to the slot 1's pins).  But why not slot 2, 3,
>4....?

How are you calling gnetlist:get-attribute-by-pinseq ?  You can only
call it on pinseq numbers that are part of the component.  And slotted
components do not have uniq pinseq numbers for different slots.

Should libgeda generate a uniq pinseq for all slots of a slotted
components?  

								-Ales



_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev