Conversion and Object Names

[Kevin McAllister]

Should objects lose their names during a conversion operation? Maybe this is a bug?

Try this. Create any 2d shape. Name it. Convert to NURBS. The object is now unnamed.

I would argue that a conversion is not a new object but just a transformed version of an existing object and therefore should retain its name after conversion.... I discovered this accidentally when working with a Marionette network that addressed a named object.

Kevin

[Benson Shaw]

Good question and discovery, Kevin.

Assuming you mean a name keyed into the name field in the  OIP Data Tab of the original object.

I agree the name should remain after conversion. Or at least I want examples or explanation of why the name should be removed by conversion. Working as Designed?

Meanwhile, it's important to know that the name field needs manual update after a Modify>Convert action.

-B

 

Edited September 10, 2016 by Benson Shaw

[Kevin McAllister]

23 minutes ago, Benson Shaw said:

Assuming you mean a name keyed into the name field in the  OIP Data Tab of the original object.

Exactly that.

KM

[AlanW]

Agree, not normally an issue in everyday working but with Marionette its an issue (appears to be ).

[PVA - Admin]

It's one of the deep issues that needs redesigning in Vectorworks' core. Any time an object changed types, it no longer keeps it's original identifier. In general work it isn't so much of a problem (Other than cases where certain types of extrudes can't be converted to Generic Solids, or have Solid operations performed on them, things like that.) but in scripting it becomes immediately obvious and a lot of coding work is done to specify "Ok now go find that new thing we made when we did A and then use it as the source object for B"

I only have a limited understanding of this problem, but it is something that is marked for change.