Skip to content
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

Limit spike length to the nearest trace. #460

Merged
merged 1 commit into from
Jul 1, 2020
Merged

Conversation

eyal0
Copy link
Contributor

@eyal0 eyal0 commented Jun 29, 2020

This is just in case the buffer operation creates a sharp corner that
leads to a very long spike, for example, if a very sharp corner is
created from a narrow trapezoid that is bg::buffered. All spikes are
limited to not cross any other trace that needs to be drawn.

@eyal0 eyal0 mentioned this pull request Jun 30, 2020
@eyal0 eyal0 force-pushed the fix_spikes branch 2 times, most recently from b0bcfc5 to 1b7b1a3 Compare June 30, 2020 23:56
@eyal0
Copy link
Contributor Author

eyal0 commented Jul 1, 2020

This will fix #412 where the spikes were too long.

@eyal0 eyal0 force-pushed the fix_spikes branch 3 times, most recently from 60a5efe to dc0fc2b Compare July 1, 2020 05:53
@coveralls
Copy link
Collaborator

coveralls commented Jul 1, 2020

Coverage Status

Coverage increased (+0.03%) to 68.153% when pulling d0cdc7d on eyal0:fix_spikes into df978ac on pcb2gcode:master.

This is just in case the buffer operation creates a sharp corner that
leads to a very long spike, for example, if a very sharp corner is
created from a narrow trapezoid that is bg::buffered.  All spikes are
limited to not cross any other trace that needs to be drawn.
@eyal0 eyal0 merged commit 640250f into pcb2gcode:master Jul 1, 2020
@eyal0 eyal0 deleted the fix_spikes branch July 1, 2020 22:32
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.

2 participants