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 suggest adding a “remaining travel” and “next action” display for the 3D CMM, similar to what we have on CNC lathes and milling machines. This would give a clear overview of where the machine will move next, helping to avoid collisions and making it easier to follow what happens during program runs or teaching.

Thanks for considering this!

Like title.

I would really like to have the toolbar/user configuration files (toolbar.dat, gbarstate.dat, et al.) to something user readable.

Like XML or JSON. When we "move" the old configuration files between versions/upgrades sometimes they end up with duplicate menu items, sometimes missing a menu item...

Today, there isn't a possibility for the user to add/edit the .dat files. This is possible with XML/JSON so the user can "see" if there is a menu item missing/duplicate. The only thing left to do is to delete the files and start over with setting up the GUI in PC-DMIS, which I find quite cumbersome.

It would be good to be able to measure hits along the flats of a round-ended slot, instead of being restricted to the radii on the ends of the slot.

When using Quick Features, Path lines do not display direction, start/end points for Cylinders. Using Auto Features (Cylinders in this case) does. This is a reason for me not to use Quick Features currently but, if these were shown graphically, just like they do for Auto Features, I would be more inclined to use them. (Quick Feature - Cylinder - TOP, Auto Cylinder - BOTTOM)

I am currently able to automate the majority of our process. However, I am unable to write anything to the properties or criteria. When I check the recorder it says "Toggle Criteria Reporting - cannot translate". When I try to program it anyway it says its read only. We use it to measure the same shape over and over and it would be much easier and less time consuming to be able to modify the criteria and properties automatically.

Like Polyworks, have the ability to measure classic Blade Geometry within PC-DMIS COP Sections. Make this functionality native to PC-DMIS CAD++ and not require the use of BLADE module. 

Slide image taken from SLS-PW plugin where Max Width, Stagger, Max Thickness, Chord Length, LE & TE Thk are all available. 

There is huge business in the UK alone for Blade inspection using Laser sensors on CMM and on Portable Arms.