Forum Replies Created
-
Posts
-
Hi. NoMachine selects the icon color depending from current theme. Please send here the output of the following command executed in a terminal window:
gsettings get org.mate.interface icon-themeHi. We’re not aware of such an issue, but it would be nice if you could contact us on forum[at]nomachine[dot]com to receive a client debug version. It would be helpful to collect some data in order to understand why the client cannot match the server stored settings.
Hi there, I am having this same problem. Please see attached image.
Hi. Could you kindly execute this command in Terminal (located in Applications => Utilities) on the machine where you don’t see the icon?
tar -czf nxclient-logs.tar.gz ~/.nx/M-*Send to forum[at]nomachine[dot]com the TAR.GZ archive. We’d like to check if you’ve problems with the image file. Thanks.
Hi.
Would it be possible in future to develop a NoMachine Android app that utilizes all available screen space?
Current version already implements immersive mode (the way to use the full screen area), but we had to disable it because it was causing issues with positioning the extended keyboard. Unluckily Android doesn’t offer a programming interface to know the geometry of the virtual keyboard, so we had to find solutions based on application layouts which clash with immersive mode. We’ll release a version addressing the issue very soon, so immersive mode will be available again.
Hi Larry. Thank you for sharing more details about your environment. The smaller window size is caused by the scaling of 125% you’re using on that monitor. You could verify this workaround:
- Right-click the NoMachine User Interface shortcut and select Properties
- Select the Compatibility tab
- Check the box “Override high DPI scaling behavior”
- Select “Application” from the combo under “Scaling performed by”
Hey Larry! Could you please check if your display is configured to use 100% of available physical area? You’ll find it in Windows Settings => System => Display.
Hi. We’re working on a version allowing to configure the authentication through SSH agent and better handling multiple factors. There are still some doubts about what to show to users and how to retrieve correct information, I’ll try to pack a testing version as soon as all changes will be completed.
Hi. We’re happy to know your experience on Chromebook! We’ve done many fixes and specific changes to support correctly Chrome OS and will keep doing it because, as you said, it’s a great opportunity for remote working.
We’re currently working on improving window initial size and resizes, and we’d like to do something for cursor images, but unluckily Android doesn’t offer easy and reliable ways to do it. As workaround you may enable showing the remote cursor.
About the mouse wheel, did you maybe notice if the experience is the same with multiple mouse models?
I’m surprised your authentication works! 😀 We don’t officially support a three-factor authentication, so I’m sure there is a lot of space for improvements. We’re doing tests in our labs to identify problems and required changes, I’ll send you an update as soon as we complete the investigation. Thank you for sharing your configuration. 🙂
Hi. What are connection details not correctly saved? Do you configure those connections with the wizard, or do you use the servers automatically discovered in LAN?
Hi mebbe. We’re aware of the uncomfortable behaviour and we’re already working on a solution.
We’d like to automatically scroll the viewport to the input position, but since X11 and MacOS look to be quite limited on that side, we’re looking for possible solutions. By the way, even if moving the viewport to the current input position will not be always possible, I’ll be sure that we reduce the size of the viewport to make the scrolling more comfortable. 🙂
Thank you for your feedback!(edited: the Feature Request associated to this is available here: https://www.nomachine.com/FR12P03758)
Hi Dan.
We’re aware of the uncomfortable behaviour and we’re already working on a solution.
In order to automatically scroll the viewport when the virtual keyboard opens, we need to know where the input caret is located. While this can be done pretty easily on Windows, X11 and macOS are quite limited and we’re still looking for the right way to retrieve that information. Any hints from our great community is more than welcome. 🙂As you probably know, it is not possible to reduce the size of the virtual keyboard to grant more space to the remote desktop, but there are multiple ways to improve the input experience:
1. If you’re on iPad you can detach or split the keyboard and move it around by keeping the input spot visible.
2. You can zoom the area and move it above the keyboard (pinch out gesture to zoom, three fingers pan to move).
3. You can connect a bluetooth keyboard to the iPhone/iPad so the virtual keyboard will not be shown. Of course this is not the best solution on the move, but it’s worth to be mentioned. 🙂At last, if you don’t use the extended keyboard you can disable it from Input settings and gain a few more valuable pixels.
Rand, we’ve found the problem occurs only on iPhone using iOS 11. This is the Trouble Report documenting it:
Virtual keyboard flickers when tapping the connection search box on iPhone with iOS 11
https://www.nomachine.com/TR06P08633We’ll release a fix in the next update, if you want you can subscribe to be notified when it will be available.
Trying to get text field “search desktop” on a connection screen. One in ten attempts was successful. Whenever I touches this text field, my keyboard arrives in a split second and hides.
ios 11.3 (15E216) at iPhone 7
Hi rand, thank you for the report. Do you’ve the same issue in portrait and landscape? Could you please verify if opening the keyboard is difficult also in another edit, like the one in Preferences => Transfers => Disallow files bigger than?
Thanks.Hi raphCode. I’m very sorry for the long delay, we had to investigate, implement proof of concepts etc etc… It took a while. 🙂
In the end we’ve considered the implementation of this Feature Request:Adding the edge scrolling method for navigating the viewport
https://www.nomachine.com/FR05P03612It’s not exactly what you have proposed, but it’s the closest solution we can implement on all supported platforms.