-
-
Notifications
You must be signed in to change notification settings - Fork 75
[Include Text][Added] Include Text preflight #746
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
What's the advantage of this over just using set_text_variable? |
Set text variables (and in general kicad variable expansions) doesn't allow newlines. I actually use set_text_variables for changelogs in the schematic (synchronised with CHANGELOG.md), but to get new lines I need to have a custom script that pads with spaces and invisible characters (\u2003), knowing in advance the width of the textbox Actually, it would be very useful to have something similar to this preflight for the schematic, so as not to have to resort to the hacky solution I had to do |
Why? I tried this: kibot:
version: 1
preflight:
set_text_variables:
- name: PRUEBITA
command: 'cat g1.sh'
outputs:
- name: 'print_sch'
comment: "Print schematic (PDF)"
type: pdf_sch_print
dir: .
options:
output: Schematic.pdfWith the Same for the PCB: Or from KiBot: |
|
You're right, looks like I was doing something wrong in my tests, feel free to close and discard this PR. Is there a way to choose an output with the set_text_variables? Here If this is not supported yet, maybe have something like: |
|
Ok, the above patch adds an option to perform expansions in the command. |
|
Thanks! |



This PR adds a new preflight
Include Text, which takes as an input TXT file(s) from an output, and adds it to the PCB. This useful for adding fabrication/assembly notes to the PCB which can be generated by the report output.On the PCB, either a text or textbox object has to be added to a group called
kibot_txt_<output_name>. The text inside the object is then modified by the preflight.