Closed mdeweerd closed 3 months ago
I was able to work around this by modifying the code in v5_sch.py to:
try:
f.x = self.x
f.y = self.y
except AttributeError as e:
print(f"**** ERROR *** no x %r" % (e,))
print(vars(self))
Following that, it appears that there were reference mismatches between the PCB and the schematic.
I need a test case for this. It might be related to some component from the PCB, not found in the schematic, and some particular filter.
Both SchematicFieldV6 and SchematicField constructors defines the x, y attributes. I can add a workaround similar to what you did, but knowing the source of the issue is much better.
Never mind, is the component that lacks x,y; which is the case for components from the PCB (where x,y is for the footprint).
Field 'x' is not found.
Using Docker on windows ghcr.io/inti-cmnb/kicad8_auto_full:latest and ghcr.io/inti-cmnb/kicad8_auto_full:dev. Both give the same result - I am checking for more details.