gEDA-dev: Broken slotting

[Steve Meier]

Stuart,

Can you post an example of how a complex component's pins and their pin
numbers would be arranged to satisfy spice?

Thanks,

Steve Meier

On Wed, 2007-09-12 at 06:44 -0400, Stuart Brorson wrote:
> >> Random question, obviously this slipped by me, but there is code that is
> >> changing the pinseq= number on the fly?  That doesn't seem right to me.
> >> I always assumed pinseq= would stay constant.
> >>
> >> -Ales
> >
> > Yes, the commit which broke the slot updating does that. It re-assigns
> > pinseq for a slotted component to be (slot-1) * num_pins higher up - so
> > the pinseq don't clash when you combine all the slots of one part.
> >
> > This is never saved out as far as I can tel, just updated in memory when
> > considering the slots.
> 
> Correct.  It is never saved out, but only used inside gnetlist.
> 
> Stuart
> 
> 
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev