> > In theory, we could support that flag in *any* object, but I'm not > sure how to manage the relationship between, say, a non-net trace on > an inner plane and the schematic/netlist. I asked someone who used a > BigName EDA package how they did it, and they had a completely > different class of object for these - a net-linking object in the > schematics, netlist, and layout. >
We use two objects for net and connectivity manipulation in schematics. Shorts, that map to a special class of footprints that can be placed on inner layers. Aliases, these map two net names to the same net and an attribute on the primary net marks it as the name it should use. Where the highest primary name in the hierarchy is used. Steve _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user