I think there is a lot of code that assumes consecutive net numbering. Instead, we could simply save net names instead of net numbers and let KiCad use net codes as convenient. One significant problem is it would cause the .kicad_pcb file format change, making it completely unreadable by the current stable.
Regards, Orson On 07/01/2017 04:49 AM, hauptmech wrote: > > We have a fairly complex board that needs to be done yesterday. We've > been experimenting with simultaneous editing of the pcb with moderate > success. > > We are using git. Each person works in a different area of the board, > and we merge the results periodically. > > Because of the time crunch, we are only focusing on what works in this > process, and staying away from edits that do not work. Moving footprints > and laying tracks works fine. > > A couple things I've noticed that could improve things: > > net indexes of nets are not stable. Maybe eeschema/netlist.cpp:369 > Maybe we could wait until we get close to running out of integers before > we do this? > > module order gets changed in some edits (Not sure but probably "fix > module file details and update modules in pcb" type edits). Ordering > modules by reference would fix this. > > > We are getting enough benefit that we'll keep refining the technique. > > > > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp