Point & Click support for GD&T Datum (MBD)

[max-mrgrsk]

Roadmap: #8350
KCL issue: #8544
KCL pr: #8417

Summary

• Add a code mod that emits gdt::datum for selected face(s)
• Wire it to: Toolbar button and Command palette

gdt::datum(
  face = side2,
  name = "A",
  framePosition = [5, 0],
  framePlane = XZ,
  fontPointSize = 36_,
  fontScale = 2.0_,
)

gdt name will be the second string use in command palette after insert

[max-mrgrsk]

Hey, @jtran KCL currently enforces single-character datum names. Is this an engine limitation or kcl? Can we relax it to support multi character names?

[jtran]

Engine limitation. It only uses the first character of any string you give it. I added a nice error message in the KCL interpreter to let users know. That's easy to remove.

[max-mrgrsk]

@nicboone8

1. what do you think should happen on the UI side if a user types an existing datum name for a new datum?
2. upon creating the new datum, should the name field be empty or A?
3. if we need a default name, should it be always A or the next available letter that is not used in the scene?
4. would you push AA names to be possible in mvp or we can leave this change for another day?

[nicboone8]

The default name should always be the next available letter. If the user manually changes the name to a letter that has already been used, we should allow them.

The "AA" style name is typically used for section views, not datums. I don't think we'll need to allow datum names exceeding a single letter

[max-mrgrsk]

@nicboone8

1. Should we allow lowercase datum names, or automatically capitalize all datum names?
2. Should datum names be limited to letters like A, B, C, or also allow numbers and other characters?

[nicboone8]

We should automatically capitalize datums.

I think we should allow numbers and characters to be used as datum names, even though it's incorrect. Maybe a lint