kicad-developers team mailing list archive

["Brian F. G. Bidulock" <bidulock@xxxxxxxxxxx>]

Lorenzo,

On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:

> On Tue, Sep 03, 2013 at 04:38:13AM -0600, Brian F. G. Bidulock wrote:
> > You don't need list of layers: just from and to--a pair.
> 
> How do you fit mask, silk and other technical layers in a range? I agree
> that it would work for copped layers. But IMHO the 'right' solution
> would be to have a pin object containing it's instances for each layer
> i.e.
> 
> Pin 1
>     Pin 1 on front
>     Pin 1 on inner 1
>     Pin 1 on inner 2
>     Pin 1 on back
>     Pin 1 on silk front
>     Pin 1 on mask front
>     Pin 1 on mask back
>     Pin 1 on assembly front
>     Pin 1 on assembly back
> 
> That would allow you to have 'true' padstacks. Vias of course could remain
> range based (unless you wanted to personalize via by layers, that could be
> overkill)

See my other note.  Just remember what layers things are on instead
of messing around with bitmasks.  So, when you place pin 1, you place
it in the cells occupied by its shape and clearance, and place it (by
reference) in the front, inner1, inner2, back copper, silk front, mask
front, assembly front and assembly back layer sets.

Any procedure wanting to find whats in those layers or cells will
simply find pin 1 there as part of the sets.  std::set union and
intersection operations are fast, and comparisons are decimated.


--brian


-- 
Brian F. G. Bidulock    � The reasonable man adapts himself to the �
bidulock@xxxxxxxxxxx    � world; the unreasonable one persists in  �
http://www.openss7.org/ � trying  to adapt the  world  to himself. �
                        � Therefore  all  progress  depends on the �
                        � unreasonable man. -- George Bernard Shaw �