Some programs may have support files like pcdmis forms, basic scripts, bitmaps, external commands, etc.  Very often, the best way to manage a program is to create a folder for it and then allow the program to reside within that folder with all its supporting files in same location.

This is because it is often impractical to have many programs in folders with all their support files intermix.

It would be nice to be able to specify whether to treat a folder as a program container that can be selected for execution.  (On main Measurement routine screen).  Bitmap association to it.

The rule would have to be that a folder name must be identical to the program name.

I know this is a complicated request.  This is how one of our customers that has 50+ CMMs has his custom interface (developed by us Hexagon) configured.

Location of programs is remote (network).

Executing measurement routine is actually a local copy of the folder and its contents.

It's a bit irritating that INSPECT always closes PC-DMIS when closing, even when PC-DMIS was already started before INSPECT.

This may not be a real problem for end users, only for those that run a lot of tests of different things...

trihedron can get too hard to see many time. should have the ability ot make it bigger (without making the graphics font bigger!)

Add auto circle for star probe

ALT+F3 is the find Hotkey, how about a hotkey for Find and Replace?

It would be nice to vary the simulation speed during offline program by either using the keyboard arrow keys or the speed setting on the jogbox - that way you can slow it down or speed it up on the fly only when you need it to without having to invoke the speed change thru a menu, etc.

Make X/Y/Z/I/J/K/Dia/etc have the ability to accept and recognize formulas (and variables/Assignments). After entering the formula it should stay active/visible for easy editing in the future.

Change the generic feature creation to include a drop down selection of previously measured features such that you could select PLN1.TX - Cir2.TY - Line3.TZ and PLN1.X - CIR2.Y - Line3.Z to populate the new generic feature as you create it.

Error messages should begin with a distinct identifying alpha-numeric code to provide a simpler means of referencing them. Otherwise, some errors messages have similar text and can be confused.