| Namespace | Windows.Devices.Midi2.Transports.Bluetooth |
|---|---|
| Type Name | MidiBluetoothConnectionState |
| Type | WinRT Enumeration (a 32-bit unsigned or signed integer) |
| IDL | MidiBluetoothConnectionStateEnum.idl |
Reported by MidiBluetoothDeviceInformation.ConnectionState.
Connecting to a Bluetooth Low Energy device isn’t quick. The service connects in the background, which takes a few seconds. And a device someone asked for keeps being tried until it shows up. So IsConnected alone can’t tell a connection that’s in progress from a device that’s just turned off. That’s why this exists.
Disconnecting a device in any state other than NotConnected cancels the request. So that’s also how you stop the service from waiting for a device that’s never coming back.
| Value | Numeric Value | Description |
|---|---|---|
NotConnected |
0 |
Not connected, and the service isn’t trying. A device that needs pairing also reports this, because the service stops trying until it’s paired |
WaitingForDevice |
1 |
Someone asked to connect, but the device hasn’t been reachable yet. The service keeps trying until the request is canceled. It tries less often the longer the device stays silent, and tries again right away when it hears the device |
Connecting |
2 |
The service is trying to connect right now, or will as soon as the attempt ahead of it finishes. The device may already be linked while its MIDI endpoint is being created |
Connected |
3 |
Connected, and its MIDI endpoint is ready to open |
An app with a connect button should usually hide or turn off that button for anything other than NotConnected, and offer disconnect instead. That way, people can’t pile up connection requests while one is already in progress.
Windows MIDI Services is an open source project with all source available on GitHub. We have a great community on Discord as well. Between GitHub and Discord, you should find the information you are looking for.
