Currently when executing from Startpoints, PCDMIS does not recognize the tip location, as stated in the Help Documentation. Is it possible for "Execute from Startpoint" to behave like "Execute from Cursor" in this respect?

Changing to file header every page template for looped programs as header gets removed after first part. 

However template removes XYZ values on geometric tolerance true positions.

Probe readout currently moves toolbars down when placed off to the side and creates white space as seen below.

The probe readout should be able to span multiple rows off to the side without pushing other toolbars down and creating a white space.

Create a dockable box for turning CAD Levels on/off, Just Like the Probe Readout is dockable.

I do think the Probe Readout window dock should span multiple toolbar lines instead of pushing toolbars onto separate line. For instance. If all of your toolbars are on the left half of the top of the screen, the probe readout should be able to sit next to them without pushing down toolbars below it. Same things for a CAD Level Dock.

Create a toggle in COMMENT/OPER, COMMENT/INPUT and COMMENT/YESNO with which you can add a standard icon like in Visual Basic:

• vbCritical

• vbQuestion

• vbExclamation

• vbInformation

If then automatic probe rotation function is on, then don't seek approval to change the angle if the suggested angle is not different than the current angle. .  

I did a search and could not find anyone else posting the same and was surprised.  However, it may very well be that there is a hidden (no pun intended) setting that forces a different behaviour.

If i have an inserted Machine model into a program and an active Probe.  I can press the Hide button in the toolbar and they will no longer be visible.  But, as soon as I execute a feature or the program whether partial or complete, everything is displayed back again.  I find the same issue happens with dimension IDs.  If as a user I am choosing to disable the display of items, why is that choice been overridden.

If that is a design intent, I would like to have a setting added so as a user I can enforce a "Stay hidden if I told you so"

Our Probe Utility Dialog has not really changed to the better as new releases are made.  I suggest efforts are placed into enhancing one dialog which is so critical to end users.  

One critical change in my view is for us to remove any checkboxes and displayed tags that do not apply to the currently opened Probe.  And present them as applicable.
One big/huge example are the checkboxes for Use Partial Calibration and Use Trax Calibration.
Use Partial Calibration is pretty much exclusive to SP25 scanning probes.  Why present/show, even if grayed out this box to a user that might be using  Camera, Laser, Touch trigger probe, etc?

TRAX calibration is exclusively for analog scanning probes and only applies to certain probes and controllers. This info is known to us.  We know which controllers (interface and Settings) have or need this calibration type.
We gray this checkbox out w/ a checked or unchecked condition because it is not applicable.  Why display it?

Our Probe Utility dialog offers tons of opportunities not only for improvement but for a better User Experience.

Its redesign is well past due.

The customer always has to manually export his XYZ file (File - Export - XYZ).
He would like to be able to write a command into the program so that it works automatically.