We have this since ages and it annoys me more and more, too. I'd regard this as a bug or as a result of not enough testing on the Hexagon side.
Scenario:
RH8 Linux, access from a Win10/11 machine via NICE DCV. ADAMS 2022.2-2024.1
Start a new session and start a dialog box. Click somewhere into the main window and the main window goes in foreground, the dbox in background (usually behind the main, so that it's unseen).
Funnily that behavior often occurs after a while of working and not directly from the beginning.
And I'd say it doesn't happen on Win that often (but that could also be the fact that I rarely use ADAMS on win to actually work on productive projects)
We have this since ages and it annoys me more and more, too. I'd regard this as a bug or as a result of not enough testing on the Hexagon side.
Scenario:
RH8 Linux, access from a Win10/11 machine via NICE DCV. ADAMS 2022.2-2024.1
Start a new session and start a dialog box. Click somewhere into the main window and the main window goes in foreground, the dbox in background (usually behind the main, so that it's unseen).
Funnily that behavior often occurs after a while of working and not directly from the beginning.
And I'd say it doesn't happen on Win that often (but that could also be the fact that I rarely use ADAMS on win to actually work on productive projects)
