SDK Server tab is misleading when running as a Windows service
Description of Bug
This is not exactly a bug, I just thought I should report it anyway.
When users choose to install OpenRGB with the Windows service, the SDK Server runs from within the service, which makes sense.
However, the SDK Server tab in the OpenRGB UI is still enabled but does not reflect the real state of the OpenRGB Server (which is not running from within the OpenRGB UI process itself).
It is misleading because:
- Users may think the SDK Server is not running, while in fact it is.
- Users may try to start the SDK Server, which will not work unless the port is not bound.
- Users may realize the port conflict issue and even try to run a second SDK Server, and that is even worse because not two instances of OpenRGB can take control of the RGB device at the same time (I think).
It would be nice if this UI was able to control the status of the Windows service itself, i.e. the Start Server button would actually start the Windows service. And show the status accordingly.
Otherwise, just grey out the whole SDK Server tab when the UI is connected to a remote server. That would probably be a simple way to clear these concerns.
Attached Log
N/A
Operating System
Hardware Configuration
N/A