On Fri, Mar 18, 2011 at 1:32 PM, DJ Delorie <d...@delorie.com> wrote: > The "core" includes the autorouters, optimizers, DRC, exporters, > reports, and even simple editing - we have a "hide vias" button. How > does that work if you no longer have "vias" as an inherent type? >
You go through and hide all the composites marked as a "via". For pcb to deal with vias differently doesn't mean that vias needs to be something fundamentally different than a footprint. On Fri, Mar 18, 2011 at 1:38 PM, DJ Delorie <d...@delorie.com> wrote: > The HID is the wrong place to be assigning *meaning* to the data. > That is still in the core. The fact that some composites are "vias" > is something intrinsic to the pcb design, independent of what color > you make it on the screen, and independend of how vias are implemented > at the lowest internal levels. >From my reading of this conversation there is a disconnect between what people are talking about w.r.t. words like the "core". Some are talking about the "lowest internal levels" where a via can just be another composite object. Some are talking about everything in pcb besides the gui, where do you need to distinguish a via from a footprint. While others seem to be using "gui" as everything but the "lowest internal levels" Jared _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user