... | ... | @@ -22,7 +22,6 @@ If your keyboard support divertable “Host Switch Channel” keys, running `sol |
|
|
…
|
|
|
```
|
|
|
|
|
|
|
|
|
Both machines must run `solaar` for the rules to work properly, and the version must be 1.1.4 or higher.
|
|
|
|
|
|
## Configuration
|
... | ... | @@ -32,10 +31,10 @@ The id for the mouse and keyboard can be found in the info-pane as the “serial |
|
|
```bash
|
|
|
solaar show | grep -iE '(serial|codename)'
|
|
|
```
|
|
|
In my case this gives
|
|
|
This may give something like
|
|
|
|
|
|
```text
|
|
|
Serial : 1E6B9EDF
|
|
|
Serial : 789ABDEF
|
|
|
Codename : MX Anywhere 3
|
|
|
Serial number: 123456AB
|
|
|
Codename : MX Keys
|
... | ... | @@ -60,9 +59,11 @@ On the first machine (“alpha”) a file is created as `~/.config/solaar/rules. |
|
|
...
|
|
|
```
|
|
|
|
|
|
In the _rule_ it is checked whether the mouse is active, and if it is then it is changed to the new host. Then the keyboard is then
|
|
|
In the _rule_ it is checked whether the mouse is active, and if it is then it is changed to the new host. Then the keyboard is changed to the new host. Finalizing the two changes a notification is posted, and that terminates the processing.
|
|
|
|
|
|
If the mouse is not active, solaar will proceed with changing the host for the keyboard, and then finalizing the change with a notification before it terminates the processing.
|
|
|
|
|
|
and on the second machine a file is created as
|
|
|
The file on the second machine (“beta”) is created as
|
|
|
|
|
|
```yaml
|
|
|
%YAML 1.3
|
... | ... | |