It would be great to add .PA, .PR in extensions for hits, arrays (...)in assignments.

Allow theoretical numbers to be locked on individual features making it possible to prevent them from changing. This would give us a more elegant solution than turning a theoretical number into an expression by dividing by 1.

I would like actually create surfaces based on a point cloud

....like the MultiExecute Wizard can do.

I absolutely love the automatic scanning parameters based on size/position/form in PC-DMIS. It's a set it, forget it thing for me. However, when it comes to the gaussian filter settings, things can get complicated. The general rule is that you need at least 7 points per undulation/wavelength. A lot of the literature talks about a given UPR/wavelength, and then changing the number of points scanned accordingly. However, the point density is automatically determined based on size/position/form, and you have little influence on the scanning path. The number of points therefore is set, and you need to change the filter settings accordingly. I use a little Excel sheet where I can enter the point density per millimeter that PC-DMIS has cooked up for me (you also need to enter the diameter for round features). The sheet will spit out the filter settings based on 8 points per undulation/wavelength (1 more than the minimum). This has worked very well for me, but it's a lot of work to set up for each feature. It's also easy to forget. Especially when scanning large diameters this can cause problems. Filtering a 500mm diameter with a point density of 6 with only 15 UPR is not ideal...

In summary: I'd love to see some kind of optional setting where you can change the filter strength based on the points per undulation/wavelength, rather than some absolute value that doesn't tell you anything without knowing the scanning density and diameter of the feature. 7 would be the minimum setting, to help prevent novices from filtering wrong. People like myself could set it to 8 and make it default. If you need a more aggressive filter, just increase the points per undulations/wavelength. Or just enter the UPR or wavelength manually, if that's your jam.

It would make it easier to follow the program and edit directly in the code at the same time

Have a way to turn off the results going red if you do not measure them, so you don't have to remeasure the entire part necessarily to turn the other results back to black and not appear out of spec in red. 

After selecting probe mode, and cursor is not at the end of the routine, the pop up that asks whether to move cursor to the end of routine, should have the option to ask again or not, and have the answer stored in Warnings under F5 settings.

It is often necessary to load PMI for local national standards. 

We want to provide many customers with an efficient experience of easily creating routines from CAD files, either directly or through optional changes to the way GD & T is calculated.