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
When using the pre-flight draw_stackup: true to draw the stackup on User.Comments, I have noticed that the total thickness dimension was drawn on User.Drawings instead of User.Comments as requested.
It means that when trying to print only User.Comments in a PDF to get a PDF report of the stackup, it is missing that dimension.
Maybe this is the intended default behaviour to keep all dimension objects on User.Drawings, but in that case would it be possible to give the user the option to change this default behaviour?
To Reproduce
Kibot 1.7.0 (using docker image ghcr.io/inti-cmnb/kicad7_auto:1.7.0) in Windows 11 WSL2-Ubuntu22, using the following command:
This fix works on my local (in WSL) install of kibot, I couldn't test inside the docker as I am not sure how to modify it or build it with that modification.
Thank you very much for your time!
The text was updated successfully, but these errors were encountered:
RemyChatel
changed the title
[BUG] In Draw Satckup preflight thickness dimension is on wrong layer
[BUG] In Draw Stackup preflight thickness dimension is on wrong layer
Jun 13, 2024
Describe the bug
When using the pre-flight
draw_stackup: true
to draw the stackup on User.Comments, I have noticed that the total thickness dimension was drawn on User.Drawings instead of User.Comments as requested.It means that when trying to print only User.Comments in a PDF to get a PDF report of the stackup, it is missing that dimension.
Maybe this is the intended default behaviour to keep all dimension objects on User.Drawings, but in that case would it be possible to give the user the option to change this default behaviour?
To Reproduce
Kibot 1.7.0 (using docker image ghcr.io/inti-cmnb/kicad7_auto:1.7.0) in Windows 11 WSL2-Ubuntu22, using the following command:
kibot.config.yaml
:kibot_stackup
kibot
using the above configurationThe result is that most of the stackup information is correctly on layer User.Comments, but the dimension for total thickness is on User.Drawings
Expected behavior
When drawing the
kibot_stackup
group on a layer, all elements of the stackup should be drawn on the same layerProposed fix
Maybe it would be sufficient to add
dim.SetLayer(layer)
in thedraw_thickness
function ofpre_draw_stackup.py
around line:KiBot/kibot/pre_draw_stackup.py
Line 276 in 9a4e671
This fix works on my local (in WSL) install of kibot, I couldn't test inside the docker as I am not sure how to modify it or build it with that modification.
Thank you very much for your time!
The text was updated successfully, but these errors were encountered: