BoxEdit doesn’t respect a sub-object selection:
It would be quite handy if it would, e.g. for changing the diameter of the hole.
2024-04-19_KillMe.3dm (84.3 KB)
I would like to know if this is merely an oversight?
We can use the Gumball to modify the sub object.
The scale handles are at the bounding box.
So I’d expect that BoxEdit would work.
Nobody cares?
Perhaps a comment from @Gijs ?
Hi @Charles
I can’t say if this is ever going to happen, but it’s not an oversight. It’s been discussed before, but I’m guessing it’s not an easy thing to implement.
https://mcneel.myjetbrains.com/youtrack/issue/RH-61960/BoxEdit-Does-not-work-with-sub-objects
-Jakob
The bounding box of the selected object is known, otherwise the Gumball wouldn’t show its scale handles correctly.
hi @Charles @Normand that YT seems about BoxEdit showing nothing, I believe this request is different and from a user perspective makes total sense that it could work.
RH-81763 BoxEdit: allow editing SubObjects
As for modifying round holes, this might help (uses PushPull):
setradius.py (2.3 KB)
I hoped to find an advantage in the WIP, but found an unexpected result instead.
While the preview makes sense, the result is completely different from the preview, and to me it looks like bad geometry.
_Selbad thinks different.
2026-06-02_BoundingBox.3dm (113.0 KB)
I was going to make a post about this. Thank you @Charles
@Charles box editing, as you can see in that YT is currently not supported.
I have read that and I know that.
Boxediting a sub selection would be a natural expectation.
If it is decided to not have this function then that’s fine.
- But then, should it be allowed to let Boxedit act on a sub selection?
- Should Boxedit produce a result at all on a sub selection?
- And should it make sick geometry, completely different from the preview?
I came across this again because this also doesn’t work: