Caret position not updating correctly in 7.2.3

Forum / NoMachine for Mac / Caret position not updating correctly in 7.2.3

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #32374
    oscahie
    Participant

    After updating both the Windows NX client and the macOS NX server to 7.2.3 I’m experiencing this new rather annoying issue. Basically the text cursor’s position is not reflected correctly on the NX client quite often. If I’m on a text editor or in Xcode and click on various different locations, soon after the caret won’t move to the last clicked position. This can go on for a while until it suddenly works again. Likewise, if I use the left and right arrow keys to move the caret, most of the time it won’t appear to move, and sometimes when it does, one or more ‘ghost’ carets will be left behind.

    Since the macOS server I’m connecting to is a laptop physically near me, I’ve verified that the caret really does move properly in both cases, so the problem seems to be only with the NX client not reflecting its real position correctly.

    I’m afraid I’ll have to downgrade back to the latest 6.x unless there’s some magic workaround for this issue 🙁

    #32446
    oscahie
    Participant

    Tried the 6.13.1 windows client with the 7.2.3 Mac server and the problem persists. After downgrading the server to 6.13.1 the problem is gone.

    Hopefully the mods/devs can confirm that this is a bug in 7.2+?

    #32497
    Britgirl
    Keymaster

    Hi, we’re not able to reproduce unfortunately. Have you also tried the latest 7.3.2 (both sides)?

     

    #32518
    oscahie
    Participant

    Yes, I’ve tried with 7.3.2 on both sides, makes no difference.

    I updated the Mac from MacOS Catalina to Big Sur and now I can only reproduce the issue on the Xcode text editor (with any text or source code file open). I’d swear it reproduced on Apple’s TextEdit app too but now it doesn’t.

    I’ve also installed NX 7.3.2 on a Mac Mini that I use as media center, also running Big Sur, and the problem is reproducible there too. Another thing I tried is switching the various display encoding options, since it feels like it could be that the NX server is not sending display updates for such small changes like the caret moving, but no luck.

    As for the affected versions, this is what I know so far:

    – 6.12.3 is working fine.
    – 6.13.1 does not have this issue but it suffers of this one other bug that messes up text selection with the mouse, so it’s basically unusable.
    – 7.1.3, 7.2.3 and 7.3.2 all have this issue.

    – The NX client version is not relevant. I’m using right now the 7.3.2 client with the 6.12.3 server.

    I could perhaps make a video of the issue, if you think it’d help?

    Also happy to try out tweaking the configuration settings if that could help.

    #32578
    Carin
    Participant

    Hi oscahie,

    Can you try to add the following line to node.cf on the server-side: DisplayAgentExtraOptions "-yuvgrab 1"
    The node.cfg is located here: /Applications/NoMachine.app/Contents/Frameworks/etc

    If the problem persists, a video will be very useful indeed. Thank you!

    #32609
    oscahie
    Participant

    Added that line to node.cfg but it made no difference, so I’ve recorded a video from the Windows machine, showing what I see on the NX client when using the arrow keys to move the caret on the Xcode editor. At the end of the video I try to move by to various positions simply clicking around the text with the mouse. And just to reiterate, the caret does move correctly on the mac running the NX server, the updates are just not sent out correctly to the NX client.

    Outside of Xcode it seems to work ok.

    #32667
    fra81
    Moderator

    Hi oscahie,

    some changes have been done in the new version 7.4.1. Can you try to install it on the server machine?

    #32683
    oscahie
    Participant

    Version 7.4.1 does seem to fix the issue! Thank you!

    #32719
    fra81
    Moderator

    Thank you for reporting!

Viewing 9 posts - 1 through 9 (of 9 total)

This topic was marked as solved, you can't post.