... | ... | @@ -126,6 +126,6 @@ For this to work the additional keys for the keyboard must be set as diverted in |
|
|
|
|
|
## Issues
|
|
|
|
|
|
One of the devices can be offline, and then be left while the other does the change. Usually the keyboard will wake up on the previous host when that happen, but occasionally I found the mouse to be the one abandoned on the previous host. That is somewhat weird. Often the state is fixed by reattempting the change once more, or changing back end then retry the change once more.
|
|
|
One of the devices can be offline, and then be left while the other does the change. It is a race condition where the device goes to sleep before the change host command commences.
|
|
|
|
|
|
To avoid typing passwords at the wrong host, possibly in some dangerous online application, it is best to use the keyboard as the controlling device if possible. That is the last fallback device is the keyboard, as that would be the one always active during the process. The keyboard is the device tested with `active` directive. |
|
|
\ No newline at end of file |
|
|
The alternate configuration hasn't an easy fix when this happen, as it isn't possible to just repeat the operation. For the _MX Anywhere 3_ mouse the fix is to use the bottom of the device to force it to reconnect with the host with the keyboard. |