On Thu, May 08, 2014 at 11:00:35AM +0200, Maciej Sumiński wrote: > In fact, that is the main advantage. I need to add settings for custom track > width/via size (that are not in netclasses or dropdown lists) and I simply > feel bad about extending an already fat class even more with new fields & > methods.
In kicad you don't worry about fat classes, they are continuosly expanding like the universe :P:P The settings class approach works fine for the plots, I think it could work. Also it could be maybe useful for some kind of 'setting templating' in the future (load/save them independently from the board). Working with different technologies could benefit from it, for example: the unsupported pads in single face have different rules than the supported ones in THT; do it wrong and they delaminate :( -- Lorenzo Marcantonio Logos Srl _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
