Default backface #9290
Draft
Default backface #9290
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
CodSpeed Performance ReportMerging #9290 will not alter performanceComparing Summary
Footnotes
|
franknoirot
reviewed
Dec 10, 2025
Comment on lines
-87
to
+88
| # [patch.crates-io] | ||
| # kcl-ezpz = { path = "../../ezpz/kcl-ezpz" } | ||
| # kittycad-modeling-cmds = { git = "https://github.com/KittyCAD/modeling-api.git", branch = "ben/chamfer_angle" } | ||
| [patch.crates-io] | ||
| kittycad-modeling-cmds = { git = "https://github.com/KittyCAD/modeling-api.git", branch = "ben/default_backface" } |
Contributor
There was a problem hiding this comment.
We should remove this patch
Contributor
Author
There was a problem hiding this comment.
Yeah will do when the modeling-api is released with the required changes
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.
Introduce a DEFAULT_BACKFACE_COLOR that is currently hard coded and sent to the engine on connection. This can be pulled in from user space with a follow-up effort