Hello,
maybe someone knows a work around. I had no problems with this snipped of code in Rhino5 but in Rhino6 it makes some strange mistakes:
Rhino.DocObjects.ObjectAttributes Attributes = new Rhino.DocObjects.ObjectAttributes();
Attributes.Name = “[DEF]Area[NAME]” + Command;
var guid = doc.Objects.AddCurve(Rec.ToNurbsCurve(), Attributes);
In Rhino5 the Name is => [DEF]Area[NAME]Command => Super Duper OK
In Rhino6 the Name is => ^[DEF]Area[NAME]Command => Error
What going on in Rhino6. I never switched because of performance issues with Rhino6 but some clients want to move to Rhino6. This is a serious bug because lots of projects are based on Naming convention.
Note that now the name isn’t [DEF]Area[NAME]Command, but "[DEF]Area[NAME]Command". It may look to the eye similar, but they are hugely different. Granted, the ^-character isn’t in front of it though.
Ok It is just a feeling. But i think for example Grasshopper seems slower and also the gui in Rhino has some nice visuals which are not Helping the Performance. This is not only a think i feel but also some others. I think the custom.objects should get priority. I think its moving away from the technical perspective towards design centric tool.