UI Smoke Tests

Test: success. 11 passed, 0 failed.
TestComplete Test Result
Workflow Run: UI Smoke Tests
Check: UI Smoke Tests

My only concern is about all these geometry nodes' name lengths. I think sometime ago, @sm6srw had to convert long named files to be in hashed value. I forgot if C3D team or Revit team documented a limitation somewhere but I would encourage us using hashed value when we can.

@QilongTang not sure what the limit is... Currently the longest Mesh file Autodesk.DesignScript.Geometry.Mesh.Translate(mesh.vector.distance)_img.jpg is shorter then other geometry help files like Autodesk.DesignScript.Geometry.TSpline.TSplineSurface.BySphereBestFit_img.jpg and Autodesk.DesignScript.Geometry.PanelSurface.ByCustomOrthogonalLattice_img.jpg.

@QilongTang I can't find the number yet that we convert files to hashed values. Since we are not longer then others I will merge and add this for follow up

Currently the longest Mesh file Autodesk.DesignScript.Geometry.Mesh.Translate(mesh.vector.distance)_img.jpg is shorter then other geometry help files like Autodesk.DesignScript.Geometry.TSpline.TSplineSurface.BySphereBestFit_img.jpg and Autodesk.DesignScript.Geometry.PanelSurface.ByCustomOrthogonalLattice_img.jpg.

@saintentropy @QilongTang

I wanted to add to this that right now we are building automations for checking these files and they currently need to follow naming of the DYN. So the . in the parentheses in these examples is causing a few issues at this time.

Autodesk.DesignScript.Geometry.Mesh.Translate(mesh.vector.distance)_img.jpg should read as ``Autodesk.DesignScript.Geometry.Mesh.Translate(mesh, vector, distance)_img.jpg`.

But if we were to use hashed values, we need to account for that in our automation as well. 🤔