You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hub/apps/design/accessibility/landmarks-and-headings.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,17 +28,17 @@ For example, when using a tab panel, consider making it a *navigation* landmark.
28
28
29
29
Whether within a landmark or even outside a landmark, consider annotating sub-elements as headings with logical heading levels.
30
30
31
-
## The Windows Settings app
31
+
## Windows Settings
32
32
33
-
The following image shows the **Ease of Access** page in a previous version of the Windows Settings app.
33
+
The following image shows the **Ease of Access** page in a previous version of Windows Settings.
34
34
35
-

35
+

36
36
37
37
For this page, the search edit box is wrapped within a search landmark, the navigation elements on the left are wrapped within a navigation landmark, and the main content on the right is wrapped within a main content landmark.
38
38
39
39
Within the navigation landmark there is a main group heading called **Ease of Access** (heading level 1) with sub-options of **Vision**, **Hearing**, and so on (heading level 2). Within the main content, **Display** is set to heading level 1 with sub-groups such as **Make everything bigger** set to heading level 2.
40
40
41
-
The Settings app would be accessible without landmarks and headings, but it becomes much more usable with them. In this case, a user with a screen reader can quickly get to the group (landmark) they're interested in, and from there they can then quickly get to the sub-group (heading).
41
+
Windows Settings would be accessible without landmarks and headings, but it becomes much more usable with them. In this case, a user with a screen reader can quickly get to the group (landmark) they're interested in, and from there they can then quickly get to the sub-group (heading).
Copy file name to clipboardExpand all lines: hub/apps/design/app-settings/guidelines-for-app-settings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ If your app allows users to choose the app's color mode, present these options u
77
77
- Dark
78
78
- Windows default
79
79
80
-
We also recommend adding a hyperlink to the Colors page of the Windows Settings app where users can access and modify the current default app mode. Use the string "Windows color settings" for the hyperlink text and `ms-settings:colors` for the URI.
80
+
We also recommend adding a hyperlink to the Colors page of Windows Settings where users can access and modify the current default app mode. Use the string "Windows color settings" for the hyperlink text and `ms-settings:colors` for the URI.
81
81
82
82

Copy file name to clipboardExpand all lines: hub/apps/design/input/touch-developer-guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -173,7 +173,7 @@ If you implement your own interaction support, keep in mind that users expect an
173
173
>
174
174
> When set to "Off", three- and four-finger interactions can be supported by apps (they will not be handled by the system).
175
175
>
176
-
> If your application must support these interactions, we recommend that you inform users of this setting and provide a link that launches the Settings app to the relevant page (ms-settings:devices-touch). For more details, see [Launch the Windows Settings app](/windows/uwp/launch-resume/launch-settings-app).
176
+
> If your application must support these interactions, we recommend that you inform users of this setting and provide a link that launches Windows Settings to the relevant page (ms-settings:devices-touch). For more details, see [Launch Windows Settings](/windows/apps/develop/launch/launch-settings).
177
177
178
178
To provide customized touch support, you can handle various [**UIElement**](/uwp/api/Windows.UI.Xaml.UIElement) events. These events are grouped into three levels of abstraction.
Copy file name to clipboardExpand all lines: hub/apps/design/signature-experiences/motion.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ Use [page transitions](../motion/page-transitions.md) to transition smoothly fro
106
106
107
107
Page transitions guide your user's eyes to incoming and outgoing content, lowering cognitive load.
108
108
109
-
:::image type="content" source="images/motion-page-transitions.png" lightbox="images/motion-page-transitions.gif" alt-text="An animated image that shows navigation between several pages in the Windows Settings app. Top-level pages slide up from the bottom. When navigating between top-level and sub-pages, pages slide left and right.":::
109
+
:::image type="content" source="images/motion-page-transitions.png" lightbox="images/motion-page-transitions.gif" alt-text="An animated image that shows navigation between several pages in Windows Settings. Top-level pages slide up from the bottom. When navigating between top-level and sub-pages, pages slide left and right.":::
Copy file name to clipboardExpand all lines: hub/apps/develop/camera/camera-privacy-setting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
12
12
13
13
# Handle the Windows camera privacy setting
14
14
15
-
Windows allows users to grant or deny access to the device's camera in the Windows Settings app, under **Privacy & Security -> Camera**. Camera access can be disabled for the entire device, for all unpackaged apps, or for individual packaged apps. This article describes the best practices for checking whether your app has access to the camera and handling the case where access is denied by the user.
15
+
Windows allows users to grant or deny access to the device's camera in Windows Settings, under **Privacy & Security -> Camera**. Camera access can be disabled for the entire device, for all unpackaged apps, or for individual packaged apps. This article describes the best practices for checking whether your app has access to the camera and handling the case where access is denied by the user.
16
16
17
17
## Check for access before initializing the camera
Copy file name to clipboardExpand all lines: hub/apps/develop/camera/camera-quickstart-winui3.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ Initialize the **MediaCapture** object by calling [InitializeAsync](/uwp/api/win
72
72
Before initializing the **MediaCapture** object we call [AppCapability.CheckAccess](/uwp/api/windows.security.authorization.appcapabilityaccess.appcapability.checkaccess) method to determine if the user has denied our app access to the camera in Windows Settings.
73
73
74
74
> [!NOTE]
75
-
> Windows allows users to grant or deny access to the device's camera in the Windows Settings app, under **Privacy & Security -> Camera**. When initializing the capture device, apps should check whether they have access to the camera and handle the case where access is denied by the user. For more information, see [Handle the Windows camera privacy setting](/windows/uwp/audio-video-camera/camera-privacy-setting).
75
+
> Windows allows users to grant or deny access to the device's camera in Windows Settings, under **Privacy & Security -> Camera**. When initializing the capture device, apps should check whether they have access to the camera and handle the case where access is denied by the user. For more information, see [Handle the Windows camera privacy setting](/windows/uwp/audio-video-camera/camera-privacy-setting).
76
76
77
77
The **InitializeAsync** call is made from inside a **try** block so that we can recover if initialization fails. Apps should handle initialization failure gracefully. In this simple example, we'll just display an error message on failure.
Copy file name to clipboardExpand all lines: hub/apps/develop/camera/camera.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This section provides guidance for creating WinUI 3 apps that use the camera or
34
34
|[Process media frames with MediaFrameReader](process-media-frames-with-mediaframereader.md)| Learn how to use a [**MediaFrameReader**](/uwp/api/Windows.Media.Capture.Frames.MediaFrameReader) with [**MediaCapture**](/uwp/api/Windows.Media.Capture.MediaCapture) to get media frames from one or more available sources, including color, depth, and infrared cameras, audio devices, or even custom frame sources such as those that produce skeletal tracking frames. This feature is designed to be used by apps that perform real-time processing of media frames, such as augmented reality and depth-aware camera apps. |
35
35
|[Process audio frames with MediaFrameReader](process-media-frames-with-mediaframereader.md)| Learn how to use a [**MediaFrameReader**](/uwp/api/Windows.Media.Capture.Frames.MediaFrameReader) with [**MediaCapture**](/uwp/api/Windows.Media.Capture.MediaCapture) to get audio data from a media frame source. |
36
36
|[Detect and respond to audio level changes by the system](detect-audio-level-changes.md)| Learn how to detect and respond to audio level changes by the system. |
37
-
|[Launch the camera settings page](launch-camera-settings.md)| Learn how to launch the Windows Settings app directly to the camera settings page. |
37
+
|[Launch the camera settings page](launch-camera-settings.md)| Learn how to launch Windows Settings directly to the camera settings page. |
38
38
|[Handle the Windows camera privacy setting](camera-privacy-setting.md)| Learn how apps should handle the Windows camera privacy setting. |
39
39
|[Connect to remote cameras](connect-to-remote-cameras.md)| Learn how to connect to remote cameras and get a **MediaFrameSourceGroup** to retrieve frames from each camera. |
description: Learn how to launch the Windows Settings app directly to the camera settings page.
2
+
description: Learn how to launch Windows Settings directly to the camera settings page.
3
3
title: Launch the camera settings page
4
4
ms.date: 11/26/2024
5
5
ms.topic: article
@@ -12,18 +12,18 @@ ms.localizationpriority: medium
12
12
13
13
# Launch the camera settings page
14
14
15
-
Windows defines a set of URIs that allow apps to launch the Windows Settings app and display a particular settings page. This article explains how to launch the Windows Settings app directly to the camera settings page and, optionally, navigate directly to the settings for a particular camera on the device. For more information, see [Launch the Windows Settings app](/windows/uwp/launch-resume/launch-settings-app).
15
+
Windows defines a set of URIs that allow apps to launch Windows Settings and display a particular settings page. This article explains how to launch Windows Settings directly to the camera settings page and, optionally, navigate directly to the settings for a particular camera on the device. For more information, see [Launch Windows Settings](/windows/apps/develop/launch/launch-settings).
16
16
17
17
## The camera settings URL
18
18
19
-
Starting with Windows 11, Build 22000, the URI `ms-settings:camera` launches the Windows Settings app and navigates to the camera settings page. Note that in previous versions of Windows, this same URI would launch the default camera application. In addition to the general camera settings page, you can append the query string parameter `cameraId` set to the symbolic link name, in escaped URI format, to launch directly to the settings page for the associated camera.
19
+
Starting with Windows 11, Build 22000, the URI `ms-settings:camera` launches Windows Settings and navigates to the camera settings page. Note that in previous versions of Windows, this same URI would launch the default camera application. In addition to the general camera settings page, you can append the query string parameter `cameraId` set to the symbolic link name, in escaped URI format, to launch directly to the settings page for the associated camera.
20
20
21
-
In the following example, the [DeviceInformation](/uwp/api/Windows.Devices.Enumeration.DeviceInformation) class is used to retrieve the symbolic link name for the first video capture device on the current machine, if one exists. Next, [LaunchUriAsync](/uwp/api/windows.system.launcher.launchuriasync) is called to launch the Windows Settings app. The `ms-settings:camera` Uri specifies that the camera settings page should be shown. The optional query string parameter `cameraId` is set to the symbolic link name for the camera, escaped with a call to [Url.EscapeDataString](/dotnet/api/system.uri.escapedatastring), to specify that the settings for the associated camera should be shown.
21
+
In the following example, the [DeviceInformation](/uwp/api/Windows.Devices.Enumeration.DeviceInformation) class is used to retrieve the symbolic link name for the first video capture device on the current machine, if one exists. Next, [LaunchUriAsync](/uwp/api/windows.system.launcher.launchuriasync) is called to launch Windows Settings. The `ms-settings:camera` Uri specifies that the camera settings page should be shown. The optional query string parameter `cameraId` is set to the symbolic link name for the camera, escaped with a call to [Url.EscapeDataString](/dotnet/api/system.uri.escapedatastring), to specify that the settings for the associated camera should be shown.
0 commit comments