Hello, Am 22.05.2018 um 00:22 schrieb Wayne Stambaugh:
[...]
> Hard coding default field names that no one can agree > upon is not going to happen. As I've stated before, I can set 10 > different designers down and I will get 10 different sets of default > field names. This really seems like me to be a configuration issue. > > [...]
The only possible solution that I would accept is to move the default field definitions from the eeschema configuration file into the default kicad project file. This way existing projects would not be polluted with the proposed default fields and users could define their own default fields in a custom project file.
I can absolutely understand your position about not hardcoding default fields.
From my point of view (and use case) moving the default field config from the eeschema config to the default kicad project file would be a very useful solution (and my guess is that many others might be OK with it, too).
Regards, Ingo _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
