I am using the Synergy app which allows sharing mouse and keyboard on another computer.
Actually, I would like to run some shell script to change some of the key mappings on another computer. So can BTT detect mouse cursor moved to a different monitor on another computer via Synergy?
If not, could you add this function for the next version?
My synergy setup: Mac (2019 late, Big Sur) as a server, Linux (CentOS 7) as a remote client.
The open source version of Synergy is Barrier (GitHub - debauchee/barrier: Open-source KVM software), and if any issues can be addressed on this it may be easier with access to the source code.
I am pretty sure the issue is with how Synergy and Barrier (S/B) pipe the mouse trigger events so there would likely need to be an extra communication path from the server computer's instance of BTT to the server computer's instance of S/B to the target computer's S/B client to the target computer's instance of BTT.
Or, create a S/B virtual device within BTT, but S/B would need to register multi-finger inputs and the like, which I am pretty sure it does not.
I'm using Barrier, and need BTT to recognize when the remote client screen is active, so I can change my gestures. The problem is that Barrier works in the background, so if I add it to the apps list in BTT, and customize the gestures for it, it doesn't work. I'd have to manually bring Barrier to the foreground every time, before moving my mouse to the remote screen. I'd appreciate it if BTT could support this use case, for example by somehow detecting that the mouse is on the remote screen, and switching to the gestures defined for Barrier even though it's in the background.
I need to change the gestures so that they'll send commands to BTT's web server on the remote client. That way I can have gestures do different actions for different apps there, rather than only sending a global keyboard shortcut via Barrier.
Ideally, BTT would support a mode where it automatically recognizes multi-touch trackpad gestures and sends a trigger signal to a remote client, via BTTs web server, if it detects that the remote is active. Then BTT on the client would interpret the gesture triggers as if they were made locally. That would avoid all the work of the user having to set up duplicate, alternate gestures to be sent to the remote, and re-interpreted there.
PS, there's a new fork of Barrier, called Input Leap. The most active contributors / maintainers have moved there. See:
I also posted some more detailed comments in the discussion area there: