Synergy-core: Server can't lock cursor to screen with hotkey

[shadda]

Operating Systems

Server: OS X El Capitan 10.11.4
Client: OS X Sierra 10.12.3

Synergy Version

1.8.8-stable-c30301e

Steps to reproduce bug

READ ME, DELETE ME: Try to be succinct. If your bug is intermittent, try and describe what you're doing when it happens most.

1. Create new hotkey on host device, keystroke(f6)
2. Assign the action "lockCursorToScreen(toggle)"
3. Hit F6 on guest machine. Log reads "cursor locked to screen", all is well.
4. Unlock and move back to host machine
5. Hit F6 on host machine and...nothing happens.

Other info

• When did the problem start to occur?
  Generally I use an OS X <-> Windows setup but for the moment I'm running dual macs. So I haven't had this exact setup in a few versions, thus it's hard to say if it only started happening in the in the 1.8.x branch.

• Is there a way to work around it?
  Doesn't seem to be, without getting a jester hat and doing something ridiculous like assigning a key for each window...

• Does this bug prevent you from using Synergy entirely?
  No.

Note that, upon hitting my toggle key on the host machine, nothing is even logged to the console.

[shadda]

Additionally, other hotkeys besides ol' faithful F6 have been tried to no avail.

[KpaBap]

Having the same issue - no matter what hotkey I bind to "Lock Cursor to Screen" nothing seems to work on the OS X server side.

[griffinqiu]

@XinyuHou Could you please fix it? I have the same issue. It blocked me....

[griffinqiu]

It is same on 10.13 High Sierra

[HaskellZhangSong]

Encountering the same problem here, too.

[kdb424]

Can confirm on Sierra that this is not working. Did work fine on my Linux server, and Mac is failing. For me this bug is critical, as my other option is to run a Linux host, but can't do that, as it's running Wayland, which is also broken.

EDIT: Managed to SOMEHOW get it working. Used Karabiner elements to map F14 to scroll lock, then set that key to lock to screen, and no clue what happened, but it seemed to work. It is worth noting I reinstalled Sierra 10.12.6 again (Both of which that were tested were fresh installed under 24 hours old) but I can confirm that something ended up making that work. 1.8.8,25a8cb2 installed through brew cask.

[griffinqiu]

Could someone help us of this issue. Version 2.0 has this issue also.

[griffinqiu]

@XinyuHou @nlyan

The issue is the server side which is MacOS cannot be trigger hot keys. It is a huge bug for as. I also tried paid 2.0. However the 2.0 version cannot config the hot keys.

Could you please fix the issue?

[nimicohgr]

+1