The plugin in object looks fantastic but not so easy to use.
[EDIT]
The 1st question is closed. I realized that I misundrestood the “fit_field” name. In fact this parameter is the name of a field in eeschema as well as the corresponding column header is “config”. Hence when the field contains the keyword, it’s not listed, provided that “ignore_dnf” = 1.
[END]
1- I can’t manage to understand how the “dnf” value in the fit_field is working. I created some additional fields in eeschema (5.1.4 release under Win 7), which I tried to fill with:
dnf
-
dnf,-
dnf, -
dnf -
with or without quotes, grouping or not.
Additionnally, i put the same strings under the fit_field value in the .ini file, whatever the ignore_dnf value is, the corresponding lines are still there in the generated html BOM file.
2- It seems that there are two different configuration files, a .ini and a .cfg.
Are they the same ? Where are they supposed to be ?
[EDIT]
still open while “Is there a relation between the .cfg file and the default “config” value for the fit_field” is closed. “config” being an eeschema field name.
[END]
3- What’s the purpose of “alt_wrap” ?
Same question for “hide_headers” and “hide_pcb_info”, the html files look the same whatever the value is false or true.
4- Is it possible, with the same .ini file, to generate two files at the same time, one in html format, the other one in tsv format ?
[EDIT]
I saw somewhere tre response but I’ve to give a try.
[END]
5- In the event I need to manage several variants of the BOM, either with all the parts, including panels, heatsinks, cables, … or the PCB supporting the pre-mounted ones only or the PCB alone, how should I configure the .ini file?
[EDIT]
I saw somewhere tre response but I’ve to give a try.
[END]
Questions 2 and 3 remain open.
Thanks for your patience.
PS sorry for the bold characters, I can’t remove the grease.
Thanks to Rene for the correction.