Today we are using Mark Set Views to run our program with PC-DMIS

Operator mode, but we might in the future want to use Inspect to run
our programs for operators. but today we have 2-3 icons in mark set views to
run different line of codes in pc dmis, so therefor it could be nice to
have the option to run mini routines from inspect. or just some lines of
the program.

The reason for this is when working with an Optiv 321 GL the controller is embedded so anytime the PCDLRN.exe is stopped the machine needs to re-home so having to wait for the machine to home every single time we want to run a new routine is a real hassle. 

Have the ability to add a Part Description or name below the icon in addition to showing the program name.  Cmm operators will be more certain they are selecting the correct program to execute.

I want to be able to calibrate probes and assign probes to the probe change rack within the Inspect Interface. I want to be able to manage probe calibrations for each program so that when I click on a measurement routine a button becomes available to calibrate all probes and angles for the associated program. Then there would be an option to manage the probe rack if needed; to assign the specific probes in the routine to the probe rack slots if not already assigned.

I want to be able to navigate within the sidebar area to inspection routines located within subfolders of the specified directory. I understand that I can go into the settings folder and call up a specific folder but it would be nice to be able to navigate the file directory within the side bar area, like Windows Explorer.

In many situations it would be better to explicitly tell INSPECT which version of PC-DMIS to run, instead of relying on the "last version that was run as administrator".

I should be able to set passwords for certain sections for operator mode. I want to choose the sections to be password protected.

Having the ability to see the report window while the report is running or even the edit screen while the program is running in Inspect would help us determine where in the program a fault occurred.  All we can see currently (In 5.1) is the CAD, %, and pass/fail screens