KiCad

It is impossible to assign component footprints from standalone eeschema

Asked by Alexey Kudryavtsev

Is this a bug or a feature? In current version of KiCad from standalone started eeschema assign component footprints cannot be done, or it cannot be done if eeschema filename differ from current project name. But it very convenient to work with eeschema files with different names, which denote for example different version of circuit. If it possible fix this.

Question information

Language:
English Edit question
Status:
Answered
For:
KiCad Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Wayne Stambaugh (stambaughw) said : 		#1

It is a feature of the recent changes in CvPcb. The netlist is passed between Eeschema and CvPcb via KiwayExpress messaging. This messaging only exists when Eeschema is built as a KiFace (basically a child window of KiCad) instead of a stand alone executable. I realize this change will take some getting used to but it has eliminated the confusion of import footprint via the netlist or the netlist/.cmp file combination since the latter has been removed from CvPcb.

Can you help with this problem?

Provide an answer of your own, or ask Alexey Kudryavtsev for more information if necessary.

To post a message you must log in.