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
Blend into extant scene #1752
Blend into extant scene #1752
Conversation
If #1751 is merged first, I can commit the documentation of the new feature here after. |
Codecov Report
@@ Coverage Diff @@
## main #1752 +/- ##
==========================================
+ Coverage 93.01% 93.19% +0.17%
==========================================
Files 271 271
Lines 39579 40372 +793
==========================================
+ Hits 36816 37623 +807
+ Misses 2763 2749 -14
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Is this a workaround for the #1747? Is it needed otherwise? I'd prefer not to merge this if not. If something like this is needed I think I'd prefer something like a |
Partly. More directly, it's a workaround for #1749. I suppose that if #1747 was fixed properly, then #1749 would be closed as well.
I don't know.
How would that work? The object I get back from |
When finished, #1797 should make the functionality for this PR redundant. |
When using
MultiScene.blend
, allow the user to bring their own scene into which the new datasets will be written. With the added flexibility this allows, the user may be able to load from a blended scene.