Forum Replies Created
-
Posts
-
Some Android versions have troubles to report the correct keyboard layout to apps, by giving instead the OS language/locale. Are your devices configured to use English (US) language?
Could you give details about your device? Model, OS (stock Android, custom ROM, etc), Kernel version, keyboard app in use (stock or custom app).
Thanks.Hi. Could you confirm the keyboard layout on Android is the same one of the remote desktop (Ubuntu)? Some versions ago we did a major rework of keyboards in order to improve multiple languages support, but using the same layout on client and server is mandatory to have a correct symbol translation.
Hi. We’re tracking your proposal here:
Implement a trackpad mode for iPhone and iPad devices
https://www.nomachine.com/FR12P03760If you want you can subscribe to show your interest and to be notified when it will be released.
Hi. We’ve published this feature request to track your proposal, you could subscribe to it to know when it’ll be released:
Can you please share the output of the following command?
xrandr -qIf the offset of display :0.1 is not 0, you may have to set it in the ‘geometry’ command line parameter, for example with this output
eDP-1 connected primary 1366x768+1920+0 (normal left inverted right x axis y axis) 309mm x 173mm HDMI-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mmthe command should be
nxplayer --geometry 1300x768+1920+0The fix has been already included in the release candidate version, so I’d say a couple of weeks. 🙂
I don’t know why you think that small RAM or screen size should prevent users from working in fullscreen mode. That option is just related to user experience, and our big efforts on optimization and performance for all screen sizes and available hardware specs are unrelated to that.
As I said we listen to our user feedback, and this is why we’re seriously evaluating your proposal. If 6 years ago you had proposed the same thing, now that option would be working differently! 😉The article is correct, but there is a problem occurring on virtual desktops, you can find here all details:
Can’t create virtual desktops having a 7680×2880 screen or above
https://www.nomachine.com/TR12N07455That may be what is preventing your configuration from working correctly. A fix will be released shortly.
Creating a graphical interface offering the best experience for as many users as possible is our main focus. The ‘match resolution’ option was added after evaluating many feedbacks, so you can be sure there are users who are enjoying it.
Nevertheless as I said we’re always focused on improving user experience, therefore we’re evaluating a way to allow to configure both resolution change options (window or screen size). In order to be effective we’ll need to skip the resize by default, and let the user choose the most suitable option. Also, resizing a physical desktop to the window size may not always be possible, because there may be some limitations on setting the display resolution to an arbitrary geometry. In such a case the desktop will be resized to a resolution among those available which is close to the one requested.OK, we spoke about that.
It’s probably one of those historical things that we left as they were, for not confusing people, but could be definitely improved.
The problem is the one-window-fits-all of the current client, where the user both navigate among the sessions and start the selected one.
Resizing the window where the user navigates was not so user-friendly, so we left the original size. But this is annoying, you are right, since it’s quite natural that, if a user selects the same session, on the same server, he will also want the same screen and window’s size.
The trick, in our opinion, is to do the resize NOT as the user clicks on connect, but AFTER the connection is negotiated and started out, as the session displays its FIRST screen! So… Going to roll out this change.
Anyway, just for your information, the next client will work in a different and, in our opinion, much better way.
There will be a window to navigate among the sessions, the users and the other resources, and sessions will start in a different window, whose size will be according to the last one selected by the user. But, for now, the change you propose is certainly for the better.Hi Maxime.
The panel you’re using for the configuration is related to server side monitors, it doesn’t list the monitor you’re using on the client, this is why you don’t see them listed.
Are you creating a virtual desktop, or are you connecting to the physical desktop of the Linux Virtual Machine?Hey there!
Please try this: when you want to disconnect from the server press Control + Alt + T (or click the small shutdown icon in the menu) and check the box “Remember current window size and position” before selecting the Disconnect or Exit action. When you will use the same connection file, the client will restore the window geometry.Could you try the option ‘-geometry’ (single dash) with the same format? As X client, the nxplayer also supports X11 command line options.
in particular nxplayer window starts in the right position but it moves to another.
What is the position of the second window move? Is it always the same? I’m wondering if the Window Manager could move the window for some reasons.
– If player is started in the full screen (use full screen resolution to set)
– if player is started in window mode disable that function/ or use window resolution to send.What you are proposing is exactly what the option “Resize remote screen” does.
If you want to pre-configure your clients in order to disable “Match resolution” option and enable the “Resize screen” option, you could create a template connection file (NXS) and distribute it to your users.
Identify these keys in the connection file and change their values accordingly:<option key="Resize the remote screen to the local geometry" value="false" /> <option key="Enable session auto-resize" value="true" />