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
_CommandBar secondary scope and supported access keys_
116
116
117
-
### Windows 10 Creators Update and older
118
-
119
-
Prior to Windows 10 Fall Creators Update, some controls, such as the CommandBar, didn't support built-in access key scopes.
120
-
121
-
The following example shows how to support CommandBar SecondaryCommands with access keys, which are available once a parent command is invoked (similar to the Ribbon in Word).
Copy file name to clipboardExpand all lines: hub/apps/develop/input/focus-navigation.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,7 @@ dev-contact: niallm
12
12
doc-status: Published
13
13
ms.localizationpriority: medium
14
14
---
15
-
# Focus navigation for keyboard, gamepad, remote control, and accessibility tools
16
-
17
-
15
+
# Focus navigation for keyboard and accessibility tools
18
16
19
17
Use focus navigation to provide comprehensive and consistent interaction experiences in your Windows apps and custom controls for keyboard power users, those with disabilities and other accessibility requirements, as well as the 10-foot experience of television screens and the Xbox One.
*Fluent Standard sizing* was created to provide a balance between information density and user comfort. Effectively, all items on the screen align to a 40x40 effective pixels (epx) target, which lets UI elements align to a grid and scale appropriately based on system level scaling.
28
-
29
-
> [!NOTE]
30
-
> For more info on effective pixels and scaling, see [Screen sizes and breakpoints](../../design/layout/screen-sizes-and-breakpoints-for-responsive-design.md#effective-pixels-and-scale-factor)
31
-
>
32
-
> For more info on system level scaling, see [Alignment, margin, padding](../../design/layout/alignment-margin-padding.md).
33
-
34
-
## Fluent Compact sizing
35
-
36
-
Applications can display a higher level of information density with *Fluent Compact sizing*. Compact sizing aligns UI elements to a 32x32 epx target, which lets UI elements to align to a tighter grid and scale appropriately based on system level scaling.
37
-
38
-
### Examples
39
-
40
-
Compact sizing can be applied at the page or grid level.
In general, set your touch target size to 7.5mm square range (40x40 pixels on a 135 PPI display at a 1.0x scaling plateau). Typically, UWP controls align with 7.5mm touch target (this can vary based on the specific control and any common usage patterns). See [Control size and density](../../design/style/spacing.md) for more detail.
27
+
In general, set your touch target size to 7.5mm square range (40x40 pixels on a 135 PPI display at a 1.0x scaling plateau). Typically, WinUI controls align with 7.5mm touch target (this can vary based on the specific control and any common usage patterns). See [Control size and density](../../design/style/spacing.md) for more detail.
63
28
64
29
These target size recommendations can be adjusted as required by your particular scenario. Here are some things to consider:
Copy file name to clipboardExpand all lines: hub/apps/develop/input/handle-pointer-input.md
+10-76Lines changed: 10 additions & 76 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,82 +40,16 @@ Windows apps can listen for the following pointer events:
40
40
> [!NOTE]
41
41
> Constrain pointer input to a specific UI element by calling [**CapturePointer**](/uwp/api/windows.ui.xaml.uielement.capturepointer) on that element within a pointer event handler. When a pointer is captured by an element, only that object receives pointer input events, even when the pointer moves outside the bounding area of the object. The [**IsInContact**](/uwp/api/windows.ui.xaml.input.pointer.isincontact) (mouse button pressed, touch or stylus in contact) must be true for **CapturePointer** to be successful.
<tdalign="left"><p>Occurs when another UI element captures the pointer, the pointer was released, or another pointer was programmatically captured.</p>
69
-
<divclass="alert">
70
-
<strong>Note</strong> There is no corresponding pointer capture event.
<tdalign="left"><p>Occurs when a pointer enters the bounding area of an element. This can happen in slightly different ways for touch, touchpad, mouse, and pen input.</p>
79
-
<ul>
80
-
<li>Touch requires a finger contact to fire this event, either from a direct touch down on the element or from moving into the bounding area of the element.</li>
81
-
<li>Mouse and touchpad both have an on-screen cursor that is always visible and fires this event even if no mouse or touchpad button is pressed.</li>
82
-
<li>Like touch, pen fires this event with a direct pen down on the element or from moving into the bounding area of the element. However, pen also has a hover state (<ahref="/uwp/api/windows.ui.xaml.input.pointer.isinrange">IsInRange</a>) that, when true, fires this event.</li>
<tdalign="left"><p>Occurs when a pointer leaves the bounding area of an element. This can happen in slightly different ways for touch, touchpad, mouse, and pen input.</p>
88
-
<ul>
89
-
<li>Touch requires a finger contact and fires this event when the pointer moves out of the bounding area of the element.</li>
90
-
<li>Mouse and touchpad both have an on-screen cursor that is always visible and fires this event even if no mouse or touchpad button is pressed.</li>
91
-
<li>Like touch, pen fires this event when moving out of the bounding area of the element. However, pen also has a hover state (<ahref="/uwp/api/windows.ui.xaml.input.pointer.isinrange">IsInRange</a>) that fires this event when the state changes from true to false.</li>
<tdalign="left"><p>Occurs when a pointer changes coordinates, button state, pressure, tilt, or contact geometry (for example, width and height) within the bounding area of an element. This can happen in slightly different ways for touch, touchpad, mouse, and pen input.</p>
97
-
<ul>
98
-
<li>Touch requires a finger contact and fires this event only when in contact within the bounding area of the element.</li>
99
-
<li>Mouse and touchpad both have an on-screen cursor that is always visible and fires this event even if no mouse or touchpad button is pressed.</li>
100
-
<li>Like touch, pen fires this event when in contact within the bounding area of the element. However, pen also has a hover state (<ahref="/uwp/api/windows.ui.xaml.input.pointer.isinrange">IsInRange</a>) that, when true and within the bounding area of the element, fires this event.</li>
<tdalign="left"><p>Occurs when the pointer indicates a press action (such as a touch down, mouse button down, pen down, or touchpad button down) within the bounding area of an element.</p>
106
-
<p><ahref="/uwp/api/windows.ui.xaml.uielement.capturepointer">CapturePointer</a> must be called from the handler for this event.</p></td>
<tdalign="left"><p>Occurs when the pointer indicates a release action (such as a touch up, mouse button up, pen up, or touchpad button up) within the bounding area of an element or, if the pointer is captured, outside the bounding area.</p></td>
<tdalign="left"><p>Occurs when the mouse wheel is rotated.</p>
115
-
<p>Mouse input is associated with a single pointer assigned when mouse input is first detected. Clicking a mouse button (left, wheel, or right) creates a secondary association between the pointer and that button through the <ahref="/uwp/api/windows.ui.xaml.uielement.pointermoved">PointerMoved</a> event.</p></td>
116
-
</tr>
117
-
</tbody>
118
-
</table>
43
+
| Event | Description |
44
+
|---|---|
45
+
|[**PointerCanceled**](/uwp/api/windows.ui.xaml.uielement.pointercanceled)| Occurs when a pointer is canceled by the platform. This can occur in the following circumstances:<ul><li>Touch pointers are canceled when a pen is detected within range of the input surface.</li><li>An active contact is not detected for more than 100 ms.</li><li>Monitor/display is changed (resolution, settings, multi-mon configuration).</li><li>The desktop is locked or the user has logged off.</li><li>The number of simultaneous contacts exceeded the number supported by the device.</li></ul> |
46
+
|[**PointerCaptureLost**](/uwp/api/windows.ui.xaml.uielement.pointercapturelost)| Occurs when another UI element captures the pointer, the pointer was released, or another pointer was programmatically captured.<br>**Note:** There is no corresponding pointer capture event. |
47
+
|[**PointerEntered**](/uwp/api/windows.ui.xaml.uielement.pointerentered)| Occurs when a pointer enters the bounding area of an element. This can happen in slightly different ways for touch, touchpad, mouse, and pen input.<ul><li>Touch requires a finger contact to fire this event, either from a direct touch down on the element or from moving into the bounding area of the element.</li><li>Mouse and touchpad both have an on-screen cursor that is always visible and fires this event even if no mouse or touchpad button is pressed.</li><li>Like touch, pen fires this event with a direct pen down on the element or from moving into the bounding area of the element. However, pen also has a hover state ([IsInRange](/uwp/api/windows.ui.xaml.input.pointer.isinrange)) that, when true, fires this event.</li></ul> |
48
+
|[**PointerExited**](/uwp/api/windows.ui.xaml.uielement.pointerexited)| Occurs when a pointer leaves the bounding area of an element. This can happen in slightly different ways for touch, touchpad, mouse, and pen input.<ul><li>Touch requires a finger contact and fires this event when the pointer moves out of the bounding area of the element.</li><li>Mouse and touchpad both have an on-screen cursor that is always visible and fires this event even if no mouse or touchpad button is pressed.</li><li>Like touch, pen fires this event when moving out of the bounding area of the element. However, pen also has a hover state ([IsInRange](/uwp/api/windows.ui.xaml.input.pointer.isinrange)) that fires this event when the state changes from true to false.</li></ul> |
49
+
|[**PointerMoved**](/uwp/api/windows.ui.xaml.uielement.pointermoved)| Occurs when a pointer changes coordinates, button state, pressure, tilt, or contact geometry (for example, width and height) within the bounding area of an element. This can happen in slightly different ways for touch, touchpad, mouse, and pen input.<ul><li>Touch requires a finger contact and fires this event only when in contact within the bounding area of the element.</li><li>Mouse and touchpad both have an on-screen cursor that is always visible and fires this event even if no mouse or touchpad button is pressed.</li><li>Like touch, pen fires this event when in contact within the bounding area of the element. However, pen also has a hover state ([IsInRange](/uwp/api/windows.ui.xaml.input.pointer.isinrange)) that, when true and within the bounding area of the element, fires this event.</li></ul> |
50
+
|[**PointerPressed**](/uwp/api/windows.ui.xaml.uielement.pointerpressed)| Occurs when the pointer indicates a press action (such as a touch down, mouse button down, pen down, or touchpad button down) within the bounding area of an element.<br>[CapturePointer](/uwp/api/windows.ui.xaml.uielement.capturepointer) must be called from the handler for this event. |
51
+
|[**PointerReleased**](/uwp/api/windows.ui.xaml.uielement.pointerreleased)| Occurs when the pointer indicates a release action (such as a touch up, mouse button up, pen up, or touchpad button up) within the bounding area of an element or, if the pointer is captured, outside the bounding area. |
52
+
| [**PointerWheelChanged**](/uwp/api/windows.ui.xaml.uielement.pointerwheelchanged) | Occurs when the mouse wheel is rotated.<br>Mouse input is associated with a single pointer assigned when mouse input is first detected. Clicking a mouse button (left, wheel, or right) creates a secondary association between the pointer and that button through the [PointerMoved](/uwp/api/windows.ui.xaml.uielement.pointermoved) event. |
0 commit comments