Forum / NoMachine for Mac / Possibly a bug on Mac client
- This topic has 2 replies, 2 voices, and was last updated 4 years, 10 months ago by kvic.
-
AuthorPosts
-
October 24, 2019 at 08:16 #24223kvicParticipant
Hi there,
I only heard about NoMachine recently and started experimenting with the free version. It grows on me everyday 🙂
I run into one (or perhaps two) nuance and hope there is a quick fix.
Both server & client are NoMachine 6.8.1. Both on macOS Mojave 10.14.6. Client machine has a Magic Trackpad and a mouse.
Issue 1
To reproduce:
- Set up a connection with “Grab the keyboard input” and “Grab the mouse input” checked.
So that (I believe) almost all key inputs including e.g. Cmd-tab & Cmd-space are sent over to the server. - Connect to server in full screen mode.
So the remote desktop of the server is one Space on the client machine. - Confirm Cmd-tab and Cmd-space indeed sent over to server
- Swipe /w four fingers on the Magic Trackpad on the client machine.
This switches to a Space of the local desktop on the client machine. - Swipe /w four fingers again back to the Space of the remote desktop.
- Left click on mouse to active key & mouse grab.
- Test Cmd-tab & Cmd-space. No longer sent over to the server.
Temporary workaround:Â Press Ctrl-Option K twice to fully activate grab key inputs again.
Related issue with a slightly modified workflow
- Replace Step 4 /w Ctrl-Option M to minimise the remote desktop.
- Replace Step 5 /w clicking NoMachine icon on the client’s Docker to go back to remote desktop.
Issue: the client’s menu bar (active app NoMachine) at the top overlays the remote desktop.
With the modified workflow, Issue 1 still persists.
If it’s a user error, pls also let me know as I’m only into NoMachine for a few weeks.
Cheers
October 31, 2019 at 18:17 #24324TorParticipantHi. I’m sorry for the slow answer, we were checking your reports.
Issue 1
We’ve identified the problem and implemented a fix, it’ll be released shortly. You can track the fix here:
https://www.nomachine.com/TR10Q09458Related issue with a slightly modified workflow
This is a little bit more tricky. The problem is related to our fullscreen mode, which is not making use of Spaces and gets confused by a particular sequence of events, causing the menu bar to be visible. There is not an easy fix for this unluckily. Our development branch uses a correct fullscreen mode, but that patch is bound to some other changes that are not ready to be released in a short time. The only workaround consists in swipe-switching to the current NoMachine Space before clicking the Dock icon, or switching the Space when the menu bar is visible to hide it.
November 18, 2019 at 09:24 #24492kvicParticipantJust installed 6.8.2 (typing this message from it). So far the fix works flawlessly. It’s a huge relief for me personally & I hope it benefits other users suffering from the same issue.
Thank you very much for the quick fix & being so helpful!
- Set up a connection with “Grab the keyboard input” and “Grab the mouse input” checked.
-
AuthorPosts
This topic was marked as solved, you can't post.