Maybe @craftyjon can shed light, does the Copper finish and other setup data end up in a Fab output anywhere? Or is this only for reference in side the Kicad project. I don’t see it anywhere in the gerber X2 data comments.
Is it possible to reference these fields via variable in Pcbnew? For instance, I generally have a fabrication notes block on the User.Comments layer that is printed to PDF as a README in the fab package. This would allow that block to be driven from the Board Settings, similar (really exactly) like the Title block is from Page Settings.
I was creating this one. It actually works, I was just working to make a Kicad package.
It also has this layers art showing the proportional thickness of the layers.
Thanks @craftyjon! I have no idea how I missed this in the v6 release. This is greatly simplifies things! Does anyone know of any board houses that actually use the extra X2 data yet? I have only seen one, and they don’t ship to the US.
No, right, yes. It’s implemented as just a group of text and graphic objects. Updating on-the-fly would be complex: every value which is used here should have a signal which this group listens to. If these values already have signals it might be worth adding listeners, but I doubt they have. Not impossible, but IMO it wouldn’t pay back. A compromise solution could be to add an “update” function to the table. With the current implementation this would require handling the group names as special cases.
For me it sounds kind of logical to trigger an update of this table when zone boundaries are re-calculated. The extra time this needs is probably negligible.
This would be a nice trick, but unreliable. Not all boards even have zones. Most do, but nobody guarantees zones are updated after some board properties are changed.
The solution should work for all tables (two at the moment).
Didn’t think of that.
Maybe change: Check zone fills before plotting into: Check zone fills and data tables before plotting, or add an extra checkbox there.
I was implementing it as a generated footprint, instantiated inside the document only, and if I click the button again, It would update the existing footprint (in my case, it would replace the whole footprint instead of replacing the field values) just keeping the original placement if this generated footprint was already instantiated before.
