I agree with all of these points and I am very happy that there now is a plan! There is one thing I would like clarified for this though.
Would It be okay to add the suggested template fields as a starting point for users? Ofcourse without the "silent" adding to symbols and netlists and boms. On Tue, 2018-05-29 at 15:55 -0400, Wayne Stambaugh wrote: > v5 point release: > > Remove the "silent" add template fields behavior from the symbol > properties dialog. > > Add a button to the symbol properties dialog to add the template > fields > to the symbol. > > Add an option in the template field option panel to add the template > fields to symbols as they are added to the schematic. > > Add a menu command and possibly a toolbar button to add the template > fields to all symbols in the schematic. > > Any adding of template fields assumes that any duplicate existing > symbol > fields will not be overwritten. > > During v6 development, I would like to see the storage of the > template > fields moved from the Eeschema config file to the default project > file. > This would allow users to define project specific template fields. I > could see this being useful for consultants who lay out boards for > multiple customers with differing BOM requirements. _______________________________________________ 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
