(Paper-Cut / Inconsistency) Layer of new Objects

Rhino
,
1

It s a small issue - but an annoying one:
There are a few commands, that do not create the new Objects on the current layer, but on the ones of the input object.
_mesh
_toNurbs (for SubD)
_booleanUnion (Delete Input = No)

this got reported already at several topics.
for example:

but let s collect all commands, that do not create a new object on the current layer !

@Gijs you may want to add above issue to your Inconsistency list)

kind regards - tom

1 Like
2

thanks Tom,

RH-89413 Mesh: option for output to current layer

RH-89414 ToNurbs: option for output to current layer

RH-89415 Booleans: option for output to current layer

1 Like
3

RH-89414 is fixed in Rhino WIP

1 Like
4

there is another one:
_chamferEdge and _filletEdge
@menno
I would claim it is more consistent if the join option is off - to have it on current layer

5

_joinCopy

→ result should be on current layer, or there should at least be an option