Keyboard shortcut bug

Forum / NoMachine for Mac / Keyboard shortcut bug

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #43544
    CrazyDef
    Participant

    Hi,

    I am using NoMachine from Windows 10 machines to control a Mac.  Everything is working fine except for one thing:  The keyboard shortcuts Ctrl+Shift+Left and Ctrl+Shift+Right.

    I have these configured in VSCode to extend the selection to the start of the previous or next word, respectively.

    When using a physical keyboard with my Mac, they work fine.  When using NoMachine, they don’t.

    I installed the Key Codes app which monitors key strokes and displays their parameters, and I noticed that the modifiers for keyboard shortcuts from the physical keyboard are different to NoMachine.

    With a physical keyboard, the key data for Ctrl+Shift+Right looks like this:

    Unicode: 63235 / 0xF703
    Key Code: 124 / 0x7C
    Modifiers: 10879235 / 0xA60103

    While with NoMachine the data looks like this:

    Unicode: 63235 / 0xF703
    Key Code: 124 / 0x7C
    Modifiers: 8782083 / 0x860103

    Looking up the bit values for the top 16 bits of the modifier keys, provides the following:

    NSEventModifierFlagCapsLock = 1 << 16, // Set if Caps Lock key is pressed.
    NSEventModifierFlagShift = 1 << 17, // Set if Shift key is pressed.
    NSEventModifierFlagControl = 1 << 18, // Set if Control key is pressed.
    NSEventModifierFlagOption = 1 << 19, // Set if Option or Alternate key is pressed.
    NSEventModifierFlagCommand = 1 << 20, // Set if Command key is pressed.
    NSEventModifierFlagNumericPad = 1 << 21, // Set if any key in the numeric keypad is pressed.
    NSEventModifierFlagHelp = 1 << 22, // Set if the Help key is pressed.
    NSEventModifierFlagFunction = 1 << 23, // Set if any function key is pressed.

    NoMachine is not setting the NSEventModifierFlagNumericPad bit.

    Reading the Apple documentation for this bit yields the following:

    NSEventModifierFlagNumericPad
    A key in the numeric keypad or an arrow key has been pressed.

    Regards,
    James

    #43572
    bucu
    Participant

    Hi,

    Indeed NoMachine is not setting that bit. We added it but it hasn’t change the behaviour for us – in both cases (with and without) VSCode was working as expected. Would you be interested in trying a debug package with that bit set and some logs enabled? If yes please contact us at forum[at]nomachine[dot]com

    #43587
    CrazyDef
    Participant

    Hi,

    Yeah, my old iMac works just fine too, but that’s probably just due to this flag being introduced in MacOS 10.12.  (My new Mac Mini where I am experiencing this problem is using the latest MacOS, obviously)

    Email sent, btw.

    Cheers,
    James

    #43772
    CrazyDef
    Participant

    Hi again,

    Just tried the debug package on my Mac Mini now. Everything is now working as expected. 🙂

    Cheers,
    James

    #43774
    Britgirl
    Participant

    Good news 🙂 Thanks for letting us know.

    #44304
    CrazyDef
    Participant

    Hi,

    Just wondering whether this fix is included in the latest release of NoMachine?  My copy is bugging me to upgrade to 8.5.3, but I don’t see anything in the release notes to suggest it is included.

    If not, do you have an ETA as to when it will be released?

    Regards,

    James

     

    #44309
    Britgirl
    Participant

    Hi, you can update to 8.5.3 because the improvements that were added to the custom package we sent to you were included in 8.5. An internal report was opened rather than a public one because we have never been able to reproduce your issue. That’s why there is no specific TR in the release notes.

    #44325
    CrazyDef
    Participant

    Ah, that’s great.

    Thanks for the clarification.  🙂

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

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