| Namespace | Windows.Devices.Midi2.Transports.Bluetooth |
|---|---|
| Type Name | MidiBluetoothPeripheralClientListConfig |
| Type | WinRT Runtime Class |
| IDL | MidiBluetoothPeripheralClientListConfig.idl |
Implements IMidiServiceTransportPluginConfig.
Writes the remembered allow and deny lists to the configuration file, so decisions made with MidiBluetoothApprovalScope.Always survive a service restart. The service applies those decisions immediately but never writes that file itself, which is why this exists as a separate step.
| Constructor | Description |
|---|---|
MidiBluetoothPeripheralClientListConfig(currentStatus) |
Builds the configuration from a MidiBluetoothPeripheralStatus. |
| Property | Description |
|---|---|
TransportId |
The Bluetooth transport’s GUID. |
ConfigJson |
The configuration file representation of both lists. |
Both lists are stored whole rather than merged entry by entry, so this must always carry the complete set. Constructing it from a MidiBluetoothPeripheralStatus fetched from the service is the reliable way to do that, because the service is what holds the current lists:
auto status = MidiBluetoothTransportManager::GetPeripheralStatus();
MidiBluetoothPeripheralClientListConfig config{ status };
MidiServiceTransportPluginConfigManager::SaveUpdate(config);
Building the lists from an application’s own copy risks writing back a stale set and dropping a decision made somewhere else in the meantime.
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.
