Skip to content

Set partition line on framing edge, not midline#805

Open
GioMusto wants to merge 2 commits intoyaqwsx:masterfrom
GioMusto:partition-line-fix
Open

Set partition line on framing edge, not midline#805
GioMusto wants to merge 2 commits intoyaqwsx:masterfrom
GioMusto:partition-line-fix

Conversation

@GioMusto
Copy link
Contributor

@GioMusto GioMusto commented Mar 9, 2025

Fix #803 by making sure partition lines are on the edge of the frame. As you can see from the comparison below, now tabs are correctly created for boards that don't span the entire length of the panel.

Before After 1st commit After 2nd commit
before_frame after_frame after_after_frame
before_railstb after_railstb
before_tightframe after_tightframe

If just the first commit is applied, some frame cuts are not generated, making the separation of the boards difficult. The second commit solves that, but generate "useless" cuts that I'm not sure it's possible to remove.

Another issue is that the frame cuts are not generated in all the other cases, making it a little bit diffucult to separate the boards in the railstb case. I also think that tightframe should generate cuts.

Finally, one thing I don't understand is the strange overlap between the frame and the backbone when using railstb. I don't know if it can be a problem (see picture).
immagine

I'm pretty new to KiKit so I don't know if the PR can break something. In any case I hope it can still be helpful in order to address #803.

@GioMusto GioMusto force-pushed the partition-line-fix branch from 356b3fe to 45cfe75 Compare March 9, 2025 15:39
@GioMusto GioMusto force-pushed the partition-line-fix branch from 96afb54 to f0519f9 Compare July 17, 2025 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unconnected tabs when putting PCBs of different sizes side by side

1 participant