You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my project I have all the parts selected from LCSC db.
Great!
But I also want to send the bom to other PCB manufacturers. It would be very useful, to be able to quickly send information from LCSC database back to schematic - like "Manufacturer Part Number" or "Manufacturer". LCSC db is really a great source of information.
One way to do it, would be just to be able to export (as .csv for example) the information given in "Part Details" popup. Then it would be easy to edit them, and paste them back to schematic/bom.
The "premium" way to do it, would be to have an selection in "Export to Schematic", which values do you want to export.
The text was updated successfully, but these errors were encountered:
I actually do not want to add more features to the export to schematic function yet as thats not a real API but a hacky solution that can break at any moment and even corrupt project files.
The KiCAD team has announced an official API for V7 but postponed it ever since.
I'll add such features once the API is available.
Maybe we could add an export to CSV but I lack the time to do that at the moment. If you want to submit a PR, feel free to do so!
In my project I have all the parts selected from LCSC db.
Great!
But I also want to send the bom to other PCB manufacturers. It would be very useful, to be able to quickly send information from LCSC database back to schematic - like "Manufacturer Part Number" or "Manufacturer". LCSC db is really a great source of information.
One way to do it, would be just to be able to export (as .csv for example) the information given in "Part Details" popup. Then it would be easy to edit them, and paste them back to schematic/bom.
The "premium" way to do it, would be to have an selection in "Export to Schematic", which values do you want to export.
The text was updated successfully, but these errors were encountered: