Lose mouse control when turning of secondary computer.

Hi,

whenever i turn off my second computer (laptop) and i'm not fast enough to move back the primary computer (desktop), i lose complete control of mouse and keyboard. It seems like Multiplicity is trying to reach the secondary computer in a loop, but shouldn't it give me back the control as soon as the connection to the secondary computer closes?

I tried to turn on my laptop again, in hope that Multiplicity can reach it again, but it didn't work.

System Information:

Windows 8 Pro x64 / Computers are connected via Gigabit LAN (not WiFi)

Thanks 

2,816 views 4 replies
Reply #1 Top

How fast is your secondary shutting down?

I've never not had time to move my cursor back to the primary.

Reply #2 Top

Hi Zubaz,

that's not the point. It's not that fast, that i don't have a chance to move back. But sometimes i click on "shutdown" and go away from desk without moving back to primary. The point is, that the software should automaticaly detect the disconnect and give control back to the main computer.

Now i know a work arround for it (moving back to primary), but i think this should be fixed.

This also could happen, if the network connection gets lost for some reason (No chance to save open important documents).

Thanks

Reply #3 Top

Quoting MegaWee, reply 2
he point is, that the software should automaticaly detect the disconnect and give control back to the main computer.
End of MegaWee's quote

The software does detect a loss of connection and returns focus to the primary.  It's just not instant so that if there is a gap in the network connection things don't instantly go wrong.

Reply #4 Top

Yes i understand, but i waited 10 minutes (went to kitchen for a coffee :P)

One thing that i noticed: Due to the frustration I tried "some" key combinations like a crazy monkey on XTC. After about 1 minute all the keys i pressed  were send to the primary computer (all at once), but i still didn't get the control back. This happend about... 3 times or so.

So maybe the used hook for input gets buggy at some point.