Tor

Forum Replies Created

Viewing 15 posts - 526 through 540 (of 594 total)
  • Author
    Posts
  • in reply to: NoMachine Monitor doesn’t respond to mouse clicks #6270
    Tor
    Participant

    Hi Sergei.
    Just send an e-mail with the link to this post for reference, we’ll contact you back.

    in reply to: NoMachine Monitor doesn’t respond to mouse clicks #6251
    Tor
    Participant

    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?

    in reply to: Menu bar has gone dark #6240
    Tor
    Participant

    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?

    in reply to: NoMachine Monitor doesn’t respond to mouse clicks #6234
    Tor
    Participant

    Hi Sergei.
    Are you using multiple monitors on this server, or do you’ve the application bar in a not standard position?

    in reply to: Availability of Retina display support #6207
    Tor
    Participant

    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/FR02M02864

    So 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.

    in reply to: Launching nxclient #6164
    Tor
    Participant

    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.

    in reply to: Drag windows on Android with mouse #5893
    Tor
    Participant

    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.

    in reply to: Menu bar has gone dark #5849
    Tor
    Participant

    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]com

    in reply to: Automatic updates doesn’t stay checked #5847
    Tor
    Participant

    Hello 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.

    in reply to: Android Keyboard Cyrillic Support #5812
    Tor
    Participant

    Thank you for the reports. We’re doing a major rework of the mobile keyboard to better support all languages. Stay tuned!

    Tor
    Participant

    Snejok, I’m sorry for the delay!
    We’ve opened this Trouble Report to document the issue: https://www.nomachine.com/TR12L04744
    A fix will be released very soon. As always, thank you for reporting and helping with this. ๐Ÿ™‚

    in reply to: Hide "Browse connections" and "New connections" from tray #5619
    Tor
    Participant

    Hi snejok.
    This was already in our roadmap, we’ve added a Feature Request so you can track it: https://www.nomachine.com/FR12L02846

    in reply to: NoMachine Android version #5558
    Tor
    Participant

    Hi Enrico.

    A rootless application requires a windowing system handling the application’s window geometry, visibility, etc. (i.e. operations that you normally do by using the window frame on a desktop OS). This kind of window management is not offered by Android so running an application in rootless mode is not allowed.

    When you run a custom session it automatically creates a virtual desktop, which explains why you don’t see two different options in the custom session configuration.

    In order to run a custom application on mobile you have a couple of options.

    ยท Run the application by using the ‘-geometry’ option, for example

    /path/to/application -geometry wxh+0+0

    where “w” and “h” are width and height of the screen of your Android device, and “+0+0” means that the origin of the window must be the origin of the display. The application will cover all the available area.

    ยท Run a script executing a window manager and your application, for example

    #!/bin/sh
    /usr/bin/metacity &
    /path/to/application

    Replace “metacity” with the window manager you prefer. You can use the window manager to maximize the application’s window like you do on desktop.

    in reply to: iOS app available for download #5537
    Tor
    Participant

    Hi NeK.

    4 the software keyboard for some reason stutters a lot (freezes for a second) while typing. this is irritating and i make all kinds of mistakes.

    We’re not aware of such a problem so we’ve started an investigation, thank you for reporting it.

    5. bluetooth keyboard support is not working correctly. almost none of the keys pass through to the server and certainly none meta keys do. please fix this as it is the single most important function of remote desktop, you can never do real work without a full keyboard. Full, including everything, meta, alt,ctrl, esc, tab, even super. else its just a toy. Please fix it too.

    A better support for bluetooth keyboard is in the pipeline, we’ll release something soon.

    6. and of course a full software keyboard is needed. Full keys, all of the standard US layout. arrows, ctrl, alt, super, home, end, prntscreen etc. that would be great.

    This is currently in testing phase and as I said in my answer to mia, it’ll be included in the next release.

    in reply to: NX Player for Android #5518
    Tor
    Participant

    We’ve published an update on Play Store right now, as always it’ll be available in a few hours. This version fixes a freeze occurring sometimes when the client connects to the remote desktop. Can you try it and let me know if it solves your issue?

Viewing 15 posts - 526 through 540 (of 594 total)