I don't think so, as, specifying x and y should be OK, as I had the same problem... I can give you two snippets, working well on awesome 3.4.4.mouse.coords( { x = 4800 - s*1920, y = 600 } )
Thanks for that - I used your code and although it does in fact move the mouse, after some more experimentation it seems the problem is that the screen gets focused and the mouse moved to (0,0) at the same time, which Synergy captures, then the mouse gets moved to the new location - but by then it's too late, Synergy has already directed input to the other machine.
Is there any way to *prevent* the mouse from being moved at all by the call to switch screens, so that I can do it manually like above? Something like awful.screen.focus(1, false) where false prevents the cursor position from being changed?
Many thanks, Adam. -- To unsubscribe, send mail to [email protected].
