Forum Replies Created
-
Posts
-
No replies yet for this issue?
My workaround is to start NoMachine on the primary monitor, connect to server, set fullscreen to off, set display resize to off, move NoMachine to secondary monitor, set fullscreen to on, set display resize to on, and log in. However, though this usually works, it isn’t guaranteed to.
Windows 8.1 is the client. The server is Mac OS, but actually this is irrelevant. I encounter the problem just starting NoMachine, without any server connected, and without it having found any servers on my network. So it is clearly a problem with the GUI. I can’t log in or do anything, even minimise the GUI, because it isn’t responding to mouse clicks.
I have two monitors on the Windows 8.1 client, my main monitor and my secondary monitor. When starting NoMachine on the secondary monitor (the one I use most often because it is much larger) it the GUI does not respond to mouse clicks, though it does respond to mouseovers. To get it to start responding to mouse clicks, I can either close it (I have to use Task Manager for this and kill the process, as it is not responding to mouse clicks to close) and open it again on the primary monitor, or I can move the app over the primary monitor using something like DisplayFusion or Active Window Manager or something like that.