Replies: 2 comments 1 reply
-
I was looking into this before and it should definitely be doable. Even if not 100% reliable, the best you can do with picking a default right now is to base your choice on desktop OS usage statistics. Having a zero-touch detection and config would be a preferred option because I'm a big fan of things that Just Work. 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Isn't the UserAgent string from the browser which opens the Deskhop web config 100% reliable to detect the guest os? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Weird idea: if we can detect the host OS, then we could handle platform-specific bits (lock, multi-screen, etc) without the user needing to configure it.
I'd suggest adding an "auto" OS type which enables detection, and use that by default if it's reliable. We'd still likely want to keep the existing OS types to override the guessing, since there are any number of things that could make it not work correctly (I'm thinking KVM but there's plenty of other possible reasons to not work).
Yeah, this is definitely out of spec, and we'd have to rely on implementation quirks that could change unexpectedly. There is an implementation of host detection in one of the TinyUSB uac2 examples (here) - it uses the ordering of descriptor requests to determine the OS. We could potentially use this or something similar.
Beta Was this translation helpful? Give feedback.
All reactions