Forum Replies Created
-
AuthorPosts
-
Tor
ParticipantThanks. This looks to be an old problem popped out again after some OS changes. Please try this: enter Settings > General > Keyboard and turn off Smart Punctuation. Let me know if this fixes it.
Tor
ParticipantThank you for the additional information. Can you please confirm your keyboard language on iPad and your layout on macOS?
May 11, 2020 at 18:37 in reply to: Connecting from a Remote Desktop session to another RDP both on same server #27362Tor
ParticipantThe default keys combination is Ctrl + Alt + End so it doesn’t interfere with the Ctrl + Alt + Del shortcut, and as you have noticed the same hotkey can be sent from the ‘special sequences’ menu. If both solutions didn’t help you we need to verify what is happening on the Windows server.
Please verify that your group policy allows services to simulate a Secure Attention Sequence (SAS). To do so, verify the policy in Computer Configuration, Administrative Templates, Windows Components, Windows Logon Options. The entry “Disable or enable software Secure Attention Sequence” must be Enabled, and the software allowed to generate the Secure Attention Sequence must be set to “Services”.
If this is not helping, please follow the instructions at https://www.nomachine.com/DT10O00162 and send gathered logs to forum[at]nomachine[dot]com.Tor
ParticipantNoMachine maps virtual keyboard symbols to symbols available in the remote keyboard layout. Some symbols like the opening or closing quotation marks are typographical and not available in the layout, so the app can’t tell the server what is the correct way to type them.
In the extended symbols you see when tapping and holding the apostrophe key, the second and the fourth symbols (attached image) will be correctly sent to the server.We’re dying for some features for iPad os such as scroll, switch desktop (by three fingers swiping on Mac), etc.
Do you mean scrolling with mouse and trackpad? As for the gestures, we’ll carefully evaluate what we can do without interfering with app gestures.
Attachments:
Tor
ParticipantHi. You could do something similar by installing
xdotool
and by executing a script like this:#!/bin/bash ids=$(xdotool search --class "nxplayer.bin") for id in $ids; do name=$(xdotool getwindowname $id) if [[ $name == "NoMachine -"* ]]; then newname=${name##NoMachine -} xdotool set_window --name "$newname" $id fi done
Tor
ParticipantHi. There seem to be an issue with the GPU acceleration in the Linux container. You can try this to work around it, by hoping next Chrome OS version will include a fix (this was not happening in Chrome OS 76, for example):
1. Open Chrome
2. In the address bar typechrome://flags/#crostini-gpu-support
3. In the opening page change the combo from “Default” to “Disabled”
4. Reboot by clicking “Restart now”As for supporting Chromebox, the reason why you see the app as not compatible should be due to the requirement of a touch interface on the device. This requirement should no longer be needed because the NoMachine app works equally well with touch and mouse input, so we’ll remove it and verify if it is enough.
Tor
ParticipantTap the wheel icon in the right side toolbar, tap Display, tap “Fit to window” to uncheck it. Session will run in 1:1 mode and it can’t be adjusted with gestures.
Tor
ParticipantHi Bryce, we’ll add you to the list of testers. Since we’re working on a version 6.9 we’ve still some things to check, but we’re also evaluating to just update a 6.1 to distribute it for testing in a shorter time. I hope we can contact you all within a couple of weeks.
Tor
ParticipantHi. We’re working on improving the mouse support on iPadOS, we’ll be sure to check wheel usage too. Thank you for the feedback!
Tor
ParticipantHaving the same issue on Pixel Slate, is it possible to be provided the APK to test as well?
@MrWoo no problem, we’ve added you to the list of testers. We’re solving some important store requirements before publishing the beta version, we’ll contact you as soon as it will be ready.I’ve heard that it is slower and that the Android version is the preferred route (is that correct NoMachine?)
@Brian where did you hear that?! 😀 Unless who said it had some very specific issues (which we would be more than happy to investigate), you can expect the same level of performance on all platforms we support. Of course there are a lot of parameters that can affect the experience and sometimes tuning the configuration could be required.April 1, 2020 at 15:45 in reply to: NoMachine – Users cannot reconnect a virtual desktop session at the last port #26433Tor
ParticipantSo at this point, I’m out of ideas for kicking off a shadow session.
We’re sorry, we ran out of coffee… The correct keystroke to force connecting through a shadow session on macOS client is
Command + Alt + Double click
, while on Linux and Windows it isControl + Alt + Double click
. We could not use the Control on macOS because it would emit a right click.Tor
ParticipantHi. In version 13 you could enable the AssistiveTouch to use the mouse with NoMachine on iPad. Now that the mouse has received a better integration in 13.4, we’ll soon explore the possibilities we have to know how to improve the app.
If you’ve any feedbacks, please share them with us!March 25, 2020 at 13:08 in reply to: Prevent scrolling of non full screen window? Dual display support? #26184Tor
ParticipantThat feature is one of those on top of our priorities, we can’t give an exact date yet, but we’ll do our best to include it in one of our next releases.
Tor
ParticipantHi. You can select the remote monitor to show in the client window, try the shortcuts
Control + Alt + A
to show them all, orControl + Alt + <monitor number>
(andControl + Alt + I
to know their numbers) to select a single monitor. You can then enable the fullscreen (or multi-window fullscreen) to match client and server monitors. However if your monitors layout and geometry on the client are different from those on the server, the result could not be the one you expect. In order to make that easier, this feature request when implemented will be helpful:March 23, 2020 at 13:16 in reply to: Prevent scrolling of non full screen window? Dual display support? #26095Tor
ParticipantIs there any way to prevent a non-full screen window (and/or non-focused window) from scrolling as the mouse travels above it?
You could try to edit the file %USERPROFILE%\.nx\config\player.cfg and reduce the value of the setting “Automatic viewport scrolling sensitive area size”. If you set it to 0, the automatic scrolling will be disabled.
We’ll start an analysis of your report to evaluate whether we need to completely prevent the automatic scrolling for an inactive window, or offer a new configuration key.But if I was to get a dual display setup at home instead of just using my laptop would the NoMachine client be able to mimic the two displays by having display #1 of work PC on display #1 of home PC and display #2 of work PC on display #2 of home PC?
If your client and server monitors layout and size will be the same, you will just need to toggle the fullscreen mode to have a perfect remote desktop match. If instead you will have different sizes or layout, the following feature request will give more freedom by allowing to place windows where you prefer:
-
AuthorPosts