Forum Replies Created
-
Posts
-
Apologies are for the computer. If I trust the Windows key on the actual keyboard, the accessibility keyboard shows the expected result and in general using the keyboard itself works. It is only when I asked for driving to send the Windows key that it does not show up on the other side. I will look over the article just in case to see if there is something not working completely.
I did notice that when I thought wasn’t inability to interact with a system dialogue was actually the mouse location being incorrectly mapped. It looked like it could be a DPI issue but I haven’t had time to look further.
I also just realized the cursor mapping is not working well. The actual cursor isn’t where I see it from the remote side
Hello. Asking Dragon to press the Windows key is not passing through at all to the Mac side. Nothing happens on the accessible keyboard.
I also notice that from the remote side (i.e. on my Windows machine) I cannot move the accessible key board with the mouse. I tried selecting grab mouse input, but it still didn’t work.
And interestingly I also noticed that the mouse from the NoMachine Windows side could not interact with any system dialogues.
Thank you for the prompt response. I actually enabled the “Grab keyboard input” already.
I am connecting to macOS 14 Sonoma from latest Windows 11.
I tried different ways of sending the Windows key from dragon and the Windows key Either simply doesn’t come through or it comes through as a tilde.
I tried to outsmart my setup by using autohotkey to map the Dragon request to a macro from Auto hotkey to send the Windows key and/or the left Windows key and I actually saw the exact same result which led me to believe that a virtual Windows key press is problematic for the NoMachine setup.
If this is expected to work, is there a way I can send you a debug trace or something?