It works for us. In all the PCBs we've made at W&L over the past five years in KiCad, I don't think any have been impacted by issues stemming from this. I don't route based on netnames--I route based on the ratsnest.
Honestly, if I were going to implement this, I might make the netnames be a concatenated list of all the labels--something like A0/MOISTURE or something like that, assuming one label was A0 and another was MOISTURE. If you're worried about netnames staying the same, though, there'd have to be a consistent ordering... But--it works for me as it is. Adam Wolf Cofounder and Engineer W&L On Sat, Jul 25, 2015 at 11:25 AM, André S. <[email protected]> wrote: > > > On July 25, 2015 6:04:18 PM GMT+02:00, Adam Wolf < > [email protected]> wrote: > > >I hate to be "this guy" (https://xkcd.com/1172/), > :D > > > >have also "seen it in the wild" quite a bit as well. > > > How do you know that net in the layout? It can have any of the labels > there. In the netlist "there can only be one". It may even change name when > doing some edit in the schematic and generating a new netlist. > > >If this were to be a warning, it would probably need to be something I > >could turn off. > Could be an option e.g. in the ERC options. I would expect a warning/error > either when doing ERC or generating the netlist. > > André > > > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
