Currently when defining a part one can supply additional kwargs:
from skidl import Part
cust_part = Part(main_lib, '0402_resistor, description='0402_10v',footprint='main_lib:0402',value=10, manf_num="panasonicseriesX",datasheet='res_0402_pansonicseriesX')
However on the generation of netlists these additional keyword arguments are not passed to the kicad netlist_gen_compnetlist generator, only the cust_part.fields are passed (additionally if kwargs of similar names are passed ie datasheet they are not updated). Is this intentional?
Potentially when parts are created with updated kwargs they could
for k, v in list(kwargs.items()):
setattr(self, k, v)
if k.capitalize() in self.fields.keys():
self.fields[k.capitalize()] = v
which replaces part information in the generated netlist. The parts loaded in kicad may not get these changes, since the parts in the library would need to update. The netlist would then store information about the parts as entered in skidl... which appear to be otherwise redundant with information loaded from kicad.
Some keywords, such as 'value' are passed to kicad, so potentially Kicad can also read these info from the netlist?
Currently when defining a part one can supply additional kwargs:
However on the generation of netlists these additional keyword arguments are not passed to the kicad
netlist_gen_compnetlist generator, only thecust_part.fieldsare passed (additionally if kwargs of similar names are passed iedatasheetthey are not updated). Is this intentional?Potentially when parts are created with updated kwargs they could
which replaces part information in the generated netlist. The parts loaded in kicad may not get these changes, since the parts in the library would need to update. The netlist would then store information about the parts as entered in skidl... which appear to be otherwise redundant with information loaded from kicad.
Some keywords, such as 'value' are passed to kicad, so potentially Kicad can also read these info from the netlist?