This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
Din41612 symbols #332
Merged
Din41612 symbols #332
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 26, 2020
|
@myfreescalewebpage |
|
Sure, sorry I have miss to do it ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is one of the tasks I wanted to get done for v6 (KiCad/kicad-symbols#2705 (comment)), and this part of it turned out to be easy enough that I will try to sneak it in now.
Triple-row symbols will take some framework, err, work, but single- and double-row symbols could be supported with the generous support already available in the script. This supports most of the DIN41612 footprints so I felt taking more time and changing a lot more stuff was a case of 'letting perfection be the enemy of good' if this can get done quickly.
Symbol PR: KiCad/kicad-symbols#2935