Forum Replies Created
-
Posts
-
Hi mr19.
The user interface doesn’t allow to select on which monitors enable the fullscreen, but your request is interesting so we’ll consider it as a proposal and we’ll evaluate to open a feature request to allow such configuration. 🙂
Hi sierrajmk.
In the new version we’ve just submitted to Apple we’ve added a Remove button in the Edit dialog, as well as a keyboard extension allowing to use modifiers and other keys normally not available in virtual keyboards.Hi memanuele.
Currently there is no way to hide the menu window, but it’ll be possible when we’ll implement this Feature Request:Running NoMachine client in kiosk mode
https://www.nomachine.com/FR02L02809Hi gpunx.
We are aware of the different behaviour on Yosemite, we’ve disabled the multi-monitor fullscreen to be compliant with the separate Spaces feature (no windows can be used across multiple displays). Even so we understand this fullscreen mode can still be useful even if the user wants to keep Displays separated, so we’re evaluating to add a new feature request to support OS X 10.10+ and span the session window across all the monitors regardless the Spaces preferences.About the Microsoft RDP client and Dual Displays, what do you mean exactly? We’re currently working on this feature, may it be related to your request?
Giving the possibility to switch between monitors of the remote server
https://www.nomachine.com/FR11K02797Hi lauraas.
Can you give more details about the server OS and NoMachine product installed (Workstation or NoMachine free)?If the server is running on Linux, the “No available sessions” message means that there are no physical desktops to connect and that you’ve no virtual desktops running. In order to create a desktop click on the “New desktop” button.
If you would rather prefer to connect to the physical desktop, then you should verify that there is an X server running on that host.This excludes the possibility that the problem is related to a particular configuration. I’d like to send you a debug version to enable more logs. If you’re willing to help, could you send your contact to forum[at]nomachine[dot]com?
Hi.
We’ve reproduced the black bar issue in our labs on a Mac mini without a monitor attached. Once the monitor was connected again, the issue disappeared. May this be your case?Hi Sergei.
Are you using multiple monitors on this server, or do you’ve the application bar in a not standard position?Hi.
We didn’t forget our retina users! 🙂
Our experience with the newer versions of Qt used on mobile clients didn’t give us solutions for the High-DPI displays, so we need to handle the request differently, and to track this change we opened some time ago this feature request:Adding an option to use native resolution on High-DPI displays
https://www.nomachine.com/FR02M02864So far we didn’t give much importance to it because, as you said, the user can always configure the desktop to use more space or he can resize the remote desktop to use a bigger resolution, but as High-DPI displays become more widespread we understand that raising the priority of this feature has become important.
Hi.
In order to work correctly the NoMachine Monitor must be connected to a NoMachine Node, so it is not meant to be launched manually.
What would you like to do?The error ‘Invalid MIT-MAGIC-COOKIE-1 key’ may be caused for example by an environment variable XAUTHORITY pointing to a file with wrong authority cookies.
Hi angelus1969.
We’re aware of issues related to hardware mouse, but the example you did sounds weird because interactions with windows should work correctly.
Can you please check if the option “Show the cursor pointer” in Input settings is enabled in your client? We’ve found a bad interaction between that option and the hardware mouse, so you need to disable it to work around the issue.Hi. We’re trying to reproduce this issue in our labs. Could you give us more details about your Mac? Do you see the black menu bar only through the NoMachine session, or also locally on Mac?
It would be great if you could send a screenshot and the output of the command “system_profiler -detailLevel mini” to issues[at]nomachine[dot]comHello noahy.
Currently Software Updates are in beta, so enabling the automatic update option is not allowed. It must always be run manually. Sorry for not making this more clear.
The good news is that we’re very close to a release supporting Software Updates, we’re currently working on our infrastructure.