Forum Replies Created
-
Posts
-
Hi NikNik.
We are aware of some problems of NoMachine mobile related to keyboard and mouse, they will be addressed soon in one of the next updates.
Hi.
We’re currently working on keyboard problems and some issues related to gestures. We’ll soon submit an update for review.
Thanks for your patience!
Hi donnek.
It appears that you left checked the option “Change the server resolution to match the client when I connect” in the last dialog shown when the session connects, or that the “Resize remote screen” option is enabled. In both cases the remote desktop tries to resize to the requested geometry or, if it is not a supported resolution, to the nearest smaller geometry that in your case may be 1280×720. In order to leave the remote desktop to the native resolution, be sure to disable the options above.
If you’ve dismissed the dialogs appearing when the session connects, you can either create a new connection or edit the configuration and check the box “Reset saved preferences and password”.Hello dhy.
We’re aware of this problem, it is due to the way Qt handles the AltGr button on Windows. We were
already planning to do something for it, but we’ve opened a public Trouble Report that you may track:https://www.nomachine.com/TR06L04476
Thanks!
Hello tagore.
Currently the right mouse button could not help to remove connection files, because the context menu is not available for the Android client. We’re evaluating different ways to restore the file removal option, but for the time being you can handle the NoMachine directory in your SD card storage by using the stock or 3rd party file browser, as you’ve already noticed.
Hello MartinS.
We’re aware of problems with the external mouse. Actually the right button acts like the Back key, so we’re working on our interface library to add this functionality. Stay tuned!
Hello Kleven, thank you for reporting this issue!
We have inserted a new Trouble Report at https://www.nomachine.com/TR06L04460
Right now the fix is under testing, so most likely it’ll be available in the next release. In the link above you can also find an option to be notified when it gets closed.Hello esarmien!
I have to say that you are the first person to have reported this particular problem of the label not being clear. The UI has been designed so that the user, when landing on the desktop list, shouldn’t have to click anything other than click the session that belongs to him. Of course, this won’t stop the user from exploring what buttons do and so on!Let’s not confuse ‘stateful buttons’ (View, Order by, My/All desktops), which let you configure how you want to view the desktop list, and ‘action buttons’ (e.g New desktop, Back, Connect) which prompt you to do something.
All the state buttons follow the same logic, i.e. the icon you see in the button is the configuration that you have in front of you. So when you see “My desktops”, you are already viewing your desktops. Adding a verb to the button, if there was space, wouldn’t solve the problem for the handful of your users who click on it. They would still click on it because they believe that by clicking on it they will see their desktops, when in fact they are already seeing their desktops.
As Britgirl mentioned, changing the logic of one button, means changing it for all the other buttons. What we need to come up with is a better label that communicates that your are already viewing your own desktops, and that by clicking on the button you will view yours and everybody else’s.
The suggestion provided by Britgirl about disabling desktop sharing could be a viable workaround if your users don’t need to share. In the meantime, we’ll evaluate what other options are possible to improve this label.
Thanks anyway for your suggestions and comments.
Hello rl2e!
If you are willing to test an APK solving this problem, please contact us at issues[at]nomachine[dot]com
(put the title of the topic in your email).As for the Back button behaviour and an option to keep the screen awake, they’re both in our roadmap.
Hello samo_dadela.
Page peel is one of those features for which it’s hard to please everyone all of the time, though we would like to and try to. 🙂 We tried to make the page-peel as inobtrusive as possible, and as configurable as possible, but at the same time keeping the GUI simple.
What about one of the remaining corners at the bottom?
Making the page-peel less sensitive would upset those who want it to appear immediately, likewise adding more options to set how sensitive it is would clutter the client GUI.
Hello ucchino.
We’ve noticed a similar problem when using custom keyboards, like Swiftkey. Can you confirm if this is your case?
Qt 5.3 recently fixed this problem, and as soon as the final version will be released we’ll upgrade our application too.
Until then you may use the Android’s stock keyboard as a workaround when running NoMachine.Hello samo_dadela!
If that is not possible at least provide a minimize hotkey… like CTRL-ALT-9 (or configurable).
The following feature that we’re implementing will allow you to minimize with a shortcut:
https://www.nomachine.com/FR04L02812– now try to exit: I can exit only with ALT-F4
If I’ve understood correctly, the behaviour you’re describing is related to the player running in fullscreen mode. In the current version you need to leave fullscreen to close the window. In one of the next updates we’ll add a close button at the bottom of the dialog that will make the operation easier.
Hi DBGTMaster.
The client can automatically start a connection if the configuration has been saved. In order to do so, when selecting the type of the session to start and when adding the session details, always check the box “Save this setting in the connection file”.Hi elquedro.
Could you send the logcat to issues[at]nomachine[dot]com referencing your forum post. Thanks!