PC-DMIS Auto Features Window disappearing repeatedly

Are you the only person who uses the machine?  The dialog windows are designed to "remember" their previous position so, if you open a dialog, move it and then close, the next time you open that dialog, it will be in the same location.  It does this by storing the co-ordinates in the settings editor.  If you are certain that nobody else is using the machine and dragging the dialogs to different locations, then the only other things I can think of are...

• Maybe there's some kind of display resolution conflict between the two monitors.
• Perhaps PC-DMIS is unable to save the dialog locations (permissions problems writing to the registry / settings editor .json files)

Are you the only person who uses the machine?  The dialog windows are designed to "remember" their previous position so, if you open a dialog, move it and then close, the next time you open that dialog, it will be in the same location.  It does this by storing the co-ordinates in the settings editor.  If you are certain that nobody else is using the machine and dragging the dialogs to different locations, then the only other things I can think of are...

• Maybe there's some kind of display resolution conflict between the two monitors.
• Perhaps PC-DMIS is unable to save the dialog locations (permissions problems writing to the registry / settings editor .json files)

Hi Neil, thanks for taking time to respond. The machine is a demo machine, we do training on it, however, no one had been on the machine besides myself when my boss opened it and the auto feature window was missing. It had also happened just a few days before during a time I was using it. The window disappears in a way that it is completely out of sight, there would be no way to drag it to the position it was, because not even a sliver of the window visible from any monitor orientation. I'm honestly not sure if the window is appearing somewhere off in space or if it is just not appearing at all. I also had an issue where my clearance cube settings editor disappeared completely once and didn't come back until I reset my user in settings editor. Is there anything that could cause the auto feature menu to not appear altogether? 

Do you have PC-DMIS open on one monitor and something else on the other or are you trying to "split" PC-DMIS between both monitors?  If it's the latter then that might be the problem.  Generally, PC-DMIS behaves much better when everything is kept on the primary monitor because that is how it was originally designed to work.

We keep everything on one monitor. We are a training facility for Hexagon, so generally PC-DMIS is on one monitor and the training material is on the other. What kind of display resolution conflict could there be? And what kind of permissions would it need writing to the registry? We have PC-DMIS always run in administrator mode by default.

Running as admin should be enough as far as permissions go, assuming you're running 2023.1 or later since those versions use .json files rather than the registry.  For older versions, you may need to go into the registry and set full read/write permission for any PC-DMIS related registry keys but that is usually only required where the IT people have been a little over zealous locking things down.

As for the monitors, try running them both in 1920x1080 resolution.  Having two monitors with a different resolution on each can sometimes cause problems.  High resolution displays can also be problematic.

Dang, I'm on 2023.2 and I've got two identical 1080p monitors. Not sure what the issue is. Thanks for trying.

Hi Cole, Not sure if this helps, but I found a similar Tech Support case, reported solution was: "ended up resetting the user and that worked."

Not necessarily a fix but more of a work-around - you could dock the dialogs rather than leave them floating.  Right click on the top of the dialog to expose the menu, select "Dockable" and then drag the dialog near to the edit window...

You can dock dialogs to the side of the edit window...

Above...

or below...

Alright thanks for the help Neil I might try that if it happens again.