Open Siege-Wizard opened 2 years ago
Gonna change the context here a bit. Due to the history of Buttplug, clients are used to handling their own scanning, and the ScanningFinished was never super reliable. While being able to control devices while a client is connected is fine, triggering scanning with no reliable event to the client seems like it could cause state issues. It'll be easier and more backwards-compatible to disallow scanning when a client is connected.
The Start/Stop scanning button toggles when you press it, but it doesn't react to
StartScanning
andStopScanning
messages from the connected client.The button should probably reflect in which state the server is and not just toggle its text when pressed.