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

PCB trace width should remember the last used value #3195

Closed
Kazade opened this issue Mar 1, 2016 · 3 comments
Closed

PCB trace width should remember the last used value #3195

Kazade opened this issue Mar 1, 2016 · 3 comments
Labels
challenging start No deep knowledge of Fritzing required, but C++ skills, a debugger and sharp focus enhancement solved
Milestone

Comments

@Kazade
Copy link
Contributor

Kazade commented Mar 1, 2016

If you are laying down your traces in PCB view it's really annoying to after every trace to change the wire thickness. I suggest that the trace thickness should be "sticky" and the next trace you draw should inherit the thickness of the last trace.

@KjellMorgenstern KjellMorgenstern added challenging start No deep knowledge of Fritzing required, but C++ skills, a debugger and sharp focus enhancement labels Nov 20, 2019
@DrItanium
Copy link
Contributor

I've been designing a ton of boards in the last two weeks and this issue kept coming up. As a addendum to this, there should be a way to denote a default width as well.

@cowboydaniel
Copy link

Image 004
Image 003
I don't know if this is new or something, but the autorouter trace width IS setable. I just found this setting, and by selecting custom, you can change the default trace width!!!

@KjellMorgenstern
Copy link
Member

@cowboydaniel The issue is not about autorouter trace width, so it is still open. PS. Please avoid cross-posting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
challenging start No deep knowledge of Fritzing required, but C++ skills, a debugger and sharp focus enhancement solved
Projects
None yet
Development

No branches or pull requests

4 participants