Minor UI (user interface) comment: White/Gray sensor initialize button is confusing:

[[Ta...]]

The top right sensor initialize button in GOM Inspect has white as "sensor initialized" and gray as "sensor closed".

I interpret white as closed or, de-initialized and gray (or any other color) as initialized.

Ambiguity in this critical button is frustrating, and is actually risky with our ScanBox.

The roll over text "initialize/close sensor" is not helpful when verifying.

For this critical button, I suggest a light blue or any other obvious color, outline indicator, or reverse, that would clearly indicates the sensor status... anything that avoids matching the surrounding application header color.

Vielen Dank!

-TadR,
UNEW, Inc.,
Stuart, FL USA

Edited Tuesday at 04:39 PM
White/Gray confusion.. even while trying to interpret the sensor status.

[[Ta...]]

To be clear: GOM Blade Inspect Pro 2022, Service Pack 6
We recently migrated from 2020, where the header is green and the sensor status is much more clear.

Also:
During a measurement, the initialized button turns off and on.
Whatever the feedback information the on/off initialize lights are supposed to provide, is not very helpful.
A non-changing status indication of sensor/light/lasers would be much more informative.
Initializing the sensor takes several seconds and we need to know for certain before selecting initialize sensor.

Edited Tuesday at 05:52 PM
Just trying to be clear.

[[Ja...]]

I think a reasonable general point, blue would seem appropriate.  It does still go from yellow to white to indicate warm up completed initialised has always been white , so i think your point is about contrast.

I haven looked for it for a long time but look for  ' dark mode' in the preferences  for the gui visualisation , this might already serve the purpose.

The laser pointers serve no real purpose in automation , but do in manual scanning , the software needs to support both.

However, it shouldnt be risky at all.  Yes the scanbox is 'live' when the sensor is initialised BUT , you have to reset the safety then press the run button , that is two clear actions that simply cannot happen by an accident , in my view anyway.

 

[[Ta...]]

Thank you James for the quick reply.
I did a quick search for "dark mode" for a change of display colors.

Yes, not having lasers on our two CORE sensors was a big loss for our high-output manual scanning operations. It made for fast scanning on our old ATOS 2M and 4M scanners.

Risky... I sometimes like to have the ATOS VMR robot on my screen go through the verified program sequence before running a new or pickup template. It's THEN that I need to be certain the sensor is not initialized. Yes, a high-contrast blue button would be a clear indicator. So eine gute Empfehlung. Vielleicht mit Ihrer Hilfe, es kann passieren!

Thank you for all you do!
-TadR

 

[[Ta...]]

I must also say:
So many times, I have executed a measurement series on our ScanBox, then found that the "software robot" is scanning because the sensor is not initialized.
Then, I must undo or re-Apply Current Parameters --> Exposure to my black-icon measurement positions.

If the sensor (light/lasers) are initialized, they should always be indicate as initialized (blue, as you suggested).
This area should indicate the absolute status, even while taking a measurements. The gray/white changes while taking a measurement creates uncertainty.

Hope this helps!