(Paper-Cut / Inconsistency) Layer of new Objects

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

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

RH-89414 is fixed in Rhino WIP

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

_joinCopy

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

_subCrv
from a Surface Edge
new Curve is on the Layer of the Surface, not on the current layer.

_variableFilletSrf
Preview Color is black - not from current Layer
(there was a similar issue with offset that got solved…?)

@Gijs did you track the points above ?

no, when joining, it should take over the first selected base object properties
RH-93793 FilletSrf commands: inherit base object properties when joined

RH-95569 JoinCopy: use current layer for output

RH-95570 _SubCrv: output to current layer

I don’t see that here (in WIP)

thanks.

yep i think we both mean the same thing:
no join → current layer
join → first selected object’s properties

ok, that is the current behavior (at least it is in the WIP)