Protege GUI apparently displaying in absent display monitor in Windows 10

[samsontu]

On Oct 13, 2018, at 12:00 PM, Campbell, James R campbell@unmc.edu wrote:

I have a problem with Protege-Windows interaction. At home I use a two screen system and in recent history the command prompt screen for Protege launched on screen 1 and I moved the client to window 2 for readability. I went on the road and did a demo but had only screen 1 functional, screen 2 was back home. Protege launched with the command screen visible on the monitor but the Protege client was not accessible. It clearly showed as an active session on the task bar but when I alt-tabbed to that session, it clearly seemed to be presenting in virtual reality on the absent screen 2. When I got home I tried configuring windows 10 only for screen 1 display, but get the same behavior EVEN AFTER reinstalling the Protege 5.5.3 software. I cannot access preferences or any other client features. No other windows software behaves this way

[samsontu]

A workaround is described in:
From: Csongor Nyulas csongor.nyulas@stanford.edu
Subject: Re: [protege-user] 5.1.0 on Windows 10 no longer working
Date: November 3, 2016 at 10:53:55 AM PDT
Also, have you, by any chance, used multiple screens at some point? Sometimes Protege can appear on a different screen which you used earlier, but it is not there any more. In such cases I will try to move the Protege window on a visible screen by using key shortcuts to get to the application window's menu. These are the shortcut keys that work on Windows and Ubuntu:
Alt + Space : opens the application window menu
M : selectes the "Move" menu item
use your mouse to move the window from the invisible screen to the visible one (make long moves to the left, right, up and down).

Csongor

[csnyulas]

This problem I could reproduce also in Ubuntu with the currently latest P5.5-beta-8.

[csnyulas]

Indeed, d32f8e0 seems to have fixed this issue. I cannot reproduce it anymore in P5.5-beta-9 snapshot.

[csnyulas]

If it works on Windows also, we can close this issue.