Skip to content

Commit ff781dd

Browse files
update glossary (#3632)
1 parent 5355d0b commit ff781dd

File tree

1 file changed

+0
-15
lines changed

1 file changed

+0
-15
lines changed

uwp/devices-sensors/lighting-dynamic-lamparray.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -106,21 +106,6 @@ The following terms and concepts are used to describe various ambient lighting s
106106

107107
Defined in the HID spec as a mode where the hardware falls back to default behavior as defined by its firmware. For example, a device might have a preprogrammed visual effect that is the default when the OS is not actively controlling the device or if the user has opted out of OS involvement for the device. The device must respond to the HID command to return from Autonomous mode to ensure smooth interaction with user expectations.
108108

109-
- AmbientLightingServer
110-
111-
A server component responsible for tracking user preferences, tracking the set of currently running ambient applications, and tracking the set of connected lighting devices. The server is responsible for taking these inputs and notifying clients (ambient effect applications) and the system of the user's policy decisions.
112-
113-
- AmbientLightingClient
114-
115-
Used by ambient applications to connect to the AmbientLightingServer, and to receive notifications of device availability based on policy decisions managed by the AmbientLightingServer and user preference. Ambient applications consume the AmbientLightingClient to receive device availability notifications.
116-
117-
- AmbientLightingManager
118-
A peer system component to the AmbientLightingServer responsible for communication with the actual hardware. The AmbientLightingServer communicates the policy decisions and the Manager component implements them.
119-
120-
- AmbientLightingHost
121-
122-
A special Windows internal effects provider.
123-
124109
- Ambient Apps
125110

126111
[**Windows.Devices.Lights**](/uwp/api/windows.devices.lights) API consumers that also have package identity and support the required app extension. Ambient apps receive notifications from the AmbientLightingClient. The events inform the app of devices they have access to. In this way, an app could show UI enumerating the connected lighting devices, and grey out the devices that are currently inaccessible due to user policy settings. Ambient Apps utilize the [**Windows.Devices.Lights**](/uwp/api/windows.devices.lights) APIs to drive effects across available devices.

0 commit comments

Comments
 (0)