gEDA-dev: Broken slotting

Stuart Brorson sdb at cloud9.net
Wed Sep 12 07:36:51 EDT 2007


>> Ummm, I guess my only question is: Why is it bad to pass around a
>> pinseq larger than the number of pins on the first slot?   Maybe I
>> need to read through this whole thread again.....
>
> Its not just passing around though.. the code actually re-writes the
> pinseq attribute on the slotted components in libgeda / gschem's
> data-structures. That is breaking the use of pinseq to index the
> device's pins (for pinnumber= updates when altering slotting).

Oh.  Then another solution is to not store the new pinseq attrib, but
rather do the modulo on the fly when spice-sdb asks for a net via
pinseq.  There was a reason I didn't do it that way, but I forget why
right now....

Stuart


More information about the geda-dev mailing list