PC-DMIS

As far as I know Program Mode is only used with Measured Features.  Makes sense to me to take it off the graphic modes toolbar and move it to where it is used.   Easier to find and semi-logical.  

Create two auto featurs  and evaluation  all individual points. The desired result would be the extreme dimensions.

Would it be possible to implement a plausibility check for PC-DMIS?
Controllable, I imagine it that way: You can define the plausibility limit in a program-related setting, e.g. deviation >10% of the tolerance is not plausible.
Ideally, this message can be sent automatically to the internal measuring program Support.

Background:
If the measuring program is started by a user, for example via the operator starter and a faulty measurement takes place, an error message should appear at the end of the measuring program or directly during evaluation that the plausibility limit has been reached.

Found the constraint on radius/diameter of Circle, but need the constraint activated on the center of circle, to calculate actual radius/diameter on very small portion of circle.

Often there are tools in auto features that are quite useful.  Often enough I spend time manually converting the coordinates of a measured feature into an autofeature to get the benefits it prescribes.

Like the title.

I use measured features a lot (placing hits with mouse/joystick) especially on surfaces/planes.

I have found it quite cumbersome to delete a certain hit from the feature, as you first need to

"find" the hit - either in the command or by using the "hits" dialog for measured features:

After that, you will need to find the actual hit in the command and remove it.

Then, repeat the procedure until all the hits you want to remove are gone.

I would like to have the possibility to multi-select the points I want to remove

through the dialog shown in the image.

Offer the same simple way to swap measured features between polar and cartesian coordinates, as is possible in auto features.

Currently, when executing profiles I've noticed it will sometimes take small segments of arcs, tiny segments, one at a time. 

It would enhance the run speed of my programs if it could execute all edges visible. 

(Side note: I've also noticed that the scan is much slower than competing products, customers have said things like "I thought It'd be faster" and my boss has even said "I remember XXX Brand being much faster, but maybe I'm wrong")