It would be usefull if the API would cover more DB.Grid methods and properties, like setting points for the leader and working with view dependant grid representation.
Currently, the 2020 API allows us to adjust grind ends (points 1 and 2) via DB.Grid..GetCurvesInView(DB.DatumExtentType.ViewSpecific, viewport), add leaders (3) and adjust bubbles (points 4 and 5 ), but is impossible to adjust the ends (points 9 and 10) of split grid line segments (6, 7 and 😎 - this adjustment is available via UI only.
What I would expect from the API:
- DB.Grid..GetCurvesInView(DB.DatumExtentType.ViewSpecific, viewport) should return al list of segments 6, 7 an 8 , while DB.Grid..GetCurvesInView(DB.DatumExtentType.Model) should return line segment from point 1 to the point 2, maybe also indicating the Z values for the Datum plane, like min(Z) for line End0 and max(Z) for line End1.
All the line segments ends should be gettable and settable. The mid-segment ("7") could be settable automagically when setting segments "6" and "8".
As an alternative approach. DB.Grid..GetCurvesInView(DB.DatumExtentType.ViewSpecific, viewport) could return an ordered list of DB.XYZ points, starting from End0 and DB.Grid..GetCurvesInView(DB.DatumExtentType.Model) coudd return 2 DB.XYZ points for min(X,Y,Z) and max (X,Y,Z)