-
Notifications
You must be signed in to change notification settings - Fork 362
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
logo part option "copper without mask" #70
Comments
In my understanding, |
I would take on this task if someone gave me a starting point, some info to work with... @el-j ? |
hej @ThomDietrich , please notice, if you want to change anything in the resource files, you have to compile fritzing from source to see the changes. maybe you could make an extra "logo"-part for testing purpose. your idea, adding a silkscreen layer simply adds a print of the logo but do not let out the white color...i think therefore the logo has to be some kind of connector but than it will be silver and not copper... like a smd pad. in conclusion: geting a copper-color for the logo is nearly impossible, a silver one should be possible if the logo itself gets a connector. if you want you could try to find a way adding the logo as a "connector" |
Any updates on this?? I am trying to add copper text to show on my PCBs too |
I would still be interested as well. Sadly I can't offer any help with the implementation... |
4 years later... No updates so far? |
I think that as @el-j said, the part needs also to have a connector like the pad part. I would create a new part. In any case, I strongly recommend you to ask this in the forum as they can probably help you there. |
To be clear, the ticket is not about copper or silver, or parts. |
When creating a logo text element on the pcb using the copper option, etching is calculated accordingly. Solder mask is however not left out, so the copper will be covered and potentially hidden. Is / Shouldn't there be an option to unmask the copper logo? (this is of course a visual more then a technical matter)
The text was updated successfully, but these errors were encountered: