Forum Replies Created
-
Posts
-
Hi.
When you launch NoMachine for the first time, it detects the local language and stores it in a configuration file. You can change it later from Settings/Appearance. Unless you’ve removed the directory $HOME/.nx when installing the new package, I could not guess a reason why this happened.
If you can’t use the UI to restore the language setting (reading German may be a difficult quest), you can close all NoMachine instances and delete the file $HOME/.nx/config/player.cfg or edit it to change the value of the key “Language” to “English”.The NoMachine application currently needs at least a 7″ display. We are going to release a version optimized for smaller displays, you may subscribe this Feature Request to be contacted when it will be available:
Offering a NoMachine client for Android smartphones
https://www.nomachine.com/FR09L02828In the meanwhile you may wish to install the APK of our tablet version by downloading it from the download area of our website. Samsung J5 display is not very big, but the application should still be usable.
Hi. The NoMachine mobile application is only a client, this is the reason why you cannot share your iPad screen.
Hi.
In order to offer as much modifiers as possible regardless the keyboard being used, the NoMachine app implements an extended keyboard bar. You can see it on top of your virtual keyboard or, if you’re using a physical keyboard, you can open it with three fingers tap or by tapping the Keyboard icon in the side toolbar. In the extended keyboard bar you’ll find Control, Esc, and other useful modifers and keys.As for the request to map keyboard modifiers depending from the remote OS, you may be interested in the following Feature Request:
Hi. Our application on iPad requires full screen view, it supports only landscape mode and it cannot use auto-layout constraints: for all these reasons it is not eligible to use Slide Over and Split View. We’ll explicitly opt out of those features to avoid to cause issues with the keyboard. Thank you for reporting it. 🙂
Client window doesn’t change size automatically except in specific cases. You could resize the window at least once while you’re connected to the remote desktop, and check the box “Remember current window size and position” in the disconnection panel (screenshot attached). If you need your window to start at a certain size, add the option
--geometry WxH[+X+Y]to the application’s shortcut.Attachments:
I assume you’re connecting to a physical desktop available on the Linux server. As soon as you connect to the remote desktop, a sequence of panels will show some tutorials and allow a quick configuration about display and audio. I’ve attached an image to show the one you must configure: uncheck the “Change the server resolution …” box to avoid to resize the remote desktop. You can then change the size of the client window without fearing to resize the desktop on Linux.
Attachments:
Hi. In order to be compliant with OS guidelines the player works in a slightly different way on macOS: there are one or more player processes running connections, and a bundle acting as an HUB for all those connections. When you want to close NoMachine on macOS you not only need to close the player process, but also the bundle. The command “open -W -a …” will return the control to the caller only when the process ‘nxdock’ will terminate.
Hi Rob.
We’re reporting the error of the OS networking layer. Those errors are very common and users are usually aware of what they mean. We’ve often considered the idea to print user friendly errors, but some of them, like those related to networking, can have a so wide set of reasons that we could give a misleading information, ending by causing more troubles instead of helping to solve them.
We’ll make sure to update our Knowledge Base to explain the error and offer some hints for the troubleshooting.
Due to some new requirements to submit the App to Apple, we may have problems to update the version currently on the store, so releasing the fix in a very short time may not be an option. The next big release, requiring a few more weeks to be ready, is already aligned with new requirements and contains a complete overhaul of keyboard events implementation, so at the moment it is the most viable solution.
Hi. We can confirm the issue, thank you for reporting it. It is documented here:
Single and double quotes no longer work after upgrading to iOS 11
https://www.nomachine.com/TR08O08032We’ll evaluate if we can release the fix as soon as possible, or include it in the next big release which is a couple of months away.
Hi.
A server configuration may help, but unluckily it is currently not working correctly. You can read about it here and maybe subscribe the Trouble Report to be notified when we’ll release the fix:https://www.nomachine.com/TR08O08009
While waiting for this fix, if you’ve control over client machines you may pre-configure a connection file and lock it down by setting it as read-only, so credentials will never be stored. Of course the drawback is that also settings changed by users will not be saved.
About console command, you can start a connection with the command
nxplayer --session <path to NXS file>. I’m not sure it is what you need, but you may give a try and tell me if it fits your needs.Hi. We only did a preliminary analysis on the devices, nevertheless we’re still very interested in supporting them, since Apple is firm in its decision to not bring mouse support on iOS. I’ve added a reference to this post in our implementation request, so we can contact you if we’ll have a beta version for our beloved guinea pigs! 😀
