-
Notifications
You must be signed in to change notification settings - Fork 37
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
Show offset planes in the scene, let user select them #4481
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…nues to work well for `startSketchOn`
if (cmd.type === 'make_plane' && range[1] !== 0) { | ||
// If we're calling `make_plane` and the code range doesn't end at `0` | ||
// it's not a default plane, but a custom one from the offsetPlane standard library function |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems pretty hacky. Can we add a flag when we create the default planes that indicate what they are?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. I was going to say something that seems like a bit of a heuristic, which I'm not a fan of. The only reason why I didn't say anything is because I think this condition will be valid for a long time to come. Maybe add a comment on top that it's a heuristic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah I just remembered that we store the IDs of the default planes in the engine command manager! I can verify that the ID is none of those; would that be concrete enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah but that would bring a dependency into ArtifactGraph. It does kinda lead to the question: why aren't we storing the default planes in the ArtifactGraph?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make an issue for this to remember to revisit later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran the branch locally and tested out the new feature. It worked well locally. Left some comments in the code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Nothing glaring. All nits.
… last commit
This avoids the autocompletion issue I was having.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4481 +/- ##
==========================================
- Coverage 86.05% 86.05% -0.01%
==========================================
Files 80 80
Lines 28762 28860 +98
==========================================
+ Hits 24751 24835 +84
- Misses 4011 4025 +14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
Closes #4468.
Implements
offset_plane_inner
to also call an engine-side effect to show a visible gray plane in the scene, and return the whole plane instead of just PlaneDatastart_sketch_on_inner
's implementation to accept full Plane definitions in addition to PlaneData.Gotchas
plane
type geometry from our default selection filter, these are not yet selectable on their own, so the user flow of "select plane -> start sketch" is not yet available.Future improvements
Demo
Screenshare.-.2024-11-13.1_24_12.PM-compressed.mp4