Option for control swapping

[JDDoesIT]

I recently was losing my mind. I had a wireless keyboard connected to the client during some troubleshooting after upgrading to the latest release. Every time I moved over to the client and tried to perform a click from the server the input method would change over to the client. I did not realize that I was hitting keys on the client keyboard while trying to use the server mouse.

I would like to get an option on the config screen to allow us to decide how we want non-server input handled. When the option screen comes out I would like a way to choose what happens.

When client input detected:

• Swap that client to server - This is what the system does now. I can see the uses for this, but most of the time it is not what I want.
• Keep input local - I can see this being my default choice as some of my systems have special keys on them. I am getting ready to add 2 or 3 monitors to my setup and rather than scroll through them all I would like the ability to reach over and tap a button or two directly on said system and then get back to my normal work flow.
• Ignore input (even on that client) - This basically locks out all input from non-server keyboards.

When I am in the field this will keep me from doing dumb stuff, and when I am home in my office it will keep my 2 year old from walking up to my desk and tapping keys messing with productivity. I could lock the door, but then the wife will not be happy. Nothing trumps wife agro.

[jml]

If you find your mind, please post the location. I've lost mine and could use the help

Your request makes sense.. I'd propose eliminating #1 and just offering 2 and 3; perhaps even a hot-key to enable/disable input on the non-server keyboards.

As to the two-year-old... he will choose your nursing home. Give [him/her] a non-connected keyboard and mouse to bang on. Works wonders.

[Nick Bolton]

This feature is planned for 2.1 which is due in about 6 months. For now, you can either wait or take a refund and use Synergy 1.