Use cylindrical placement for key legends #199
Draft
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 makes the depth of the legend approximately the same across the whole dish, instead of varying
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed that when placing legends on cherry keycaps, the depth varies across the key. This is because the text is placed on a plane, not along the curve of the top key surface.
I'm printing resin keycaps then adding color legends using gel nail polish; I think that having consistent depth of the inset legends will lead to better results.
I investigated options to correct this. One possibility is the openscad "text on" library. Of course, this library comes with its own set of caveats, many resulting from the fact that it's not possible to directly measure text metrics from within scad code.
Here's the result of my experimentation. I don't think it's suitable to merge in its current state, so please consider this a possible starting point for discussion.
This copies in the text_on library, which I believe is licensed compatibly (LGPL 2.1 upgrades to GPL2-or-later, which in turn upgrades to GPL3).
Please feel free to close this up if it's not a direction you're interested in pursuing. In any case, thanks for KeyV2.