It is worth noting that the translation of rightmiddle click events are correctly handled when running with OSX as the server (using the mapMacButtonToSynergy function), we simply needed to handle it similarly on the client side firefox) is because they might hook into a lower API for intercepting mouse clicks and look at the button passed to the API, but thats just a guess. I believe the reason for some applications correctly handling the middle click (ie. Events don't match what they should be, and the click is incorrectly handled.OSX Client lookup the system event to send, here it will send kCGEventRightMouseDown event with the button id of the middle button.Synergy send button press event to the client of button id 2.The OS would correctly handle the second button (right mouse button) being clicked.OSX Client lookup the system event to send, in this case it would send the kCGEventOtherMouseDown event with a button id of the right mouse button.Synergy sends a button press event to the client of button id 3.My pull-request correctly translates the incoming events so that button index as well as the actual mouse event are sent correctly the the OS.īelow is an example flow for a right click and a middle click before:
#Os x 10.7 synergykm mac#
For other OS's left button is id 1, middle is 2 and right button is 3, however on Mac they have flipped right and middle buttons so middle button is 3 and right button is 2. Basically this is down to mouse events not being correctly translated from Synergy to Mac. I just submitted a pull-request that should fix this.
0 kommentar(er)
