Closed kaechele closed 4 years ago
Ignore this comment.
I believe this request to be unrelated to the issue I described. My issue is with a platform specific layout being applied to the keyboard on Windows and Mac and the lack thereof on Linux which can have unexpected side effects depending on which layout was last applied before the user boots into or connects a Linux system. I believe the person you pointed to this issue is referring to the K850's feature of being able to switch between 3 different devices (Bluetooth or Unifying) and a potential ability of the protocol to set the keyboard to one of those three options from the host side.
Yeah, right. Sorry for the confusion.
In principle it would not be too hard to implement this feature, but I don't have documentation on how it is supposed to work. @FFY00 Do you have documentation on this feature (4351 probably)?
Getting documentation on features is a slow process. I have requests for documentation on features where Solaar is not behaving correctly and I want to get this documentation before asking for Multiplatform.
@kaechele PR #841 should solve your problem. It has had some testing but it would be nice to have it tested some more.
To test a pull request, first download Solaar from this repository if you have not already done so and cd to the download directory. The first time you test the pull request, fetch it into a new branch and checkout that branch, as in (where 841 is the number of the pull request):
git fetch origin pull/841/head:pull_841
git checkout pull_841
Run Solaar as bin/solaar
and see whether you have a setting named "Set OS" and whether your changeable keys change when you change that setting.
Unfortunately, no dice on my K850: Only multiplatform related debug output:
15:36:06,806 ERROR [ReceiverListener:hidraw0] logitech_receiver.settings_templates: check_feature[MULTIPLATFORM] inconsistent feature 0 (Android ) already known
@kaechele I think I know what went wrong but I'll need the output before that error message - about 30 lines worth.
This is the entire output from Solaar once the device comes on:
```
15:50:03,618 DEBUG [ReceiverListener:hidraw0] logitech_receiver.base: (19) => r[10 02 4104 B16240]
15:50:03,629 INFO [ReceiverListener:hidraw0] solaar.listener: Notification(2,41,04,B16240) triggered new device
Grr, Python, grr. Zero is not false!
@kaechele Should be fixed now.
Thanks! I have tested it again and can now switch between OS layouts. Changing the OS does affect the assignment of keys so I assume it is working as intended. If you'd like I can also test the use case I described earlier: Using the same receiver with multiple platforms and seeing if the layout is automatically switched to Windows (or maybe in fact whatever I chose last in Solaar) when I boot the Linux machine.
That should work, but it would be good to test. Solaar should force the same layout as the last time the device was visible to Solaar.
Information
solaar show
for the target device (if applicable):