Use visual feedback to show users when their interactions are detected, interpreted, and handled.
Visual feedback can help users by encouraging interaction. It indicates the success of an interaction, which improves the user's sense of control. It also relays system status and reduces errors.
Important APIs: Windows.Devices.Input, Windows.UI.Input, Windows.UI.Core
For more info, see ShowGestureFeedback.
Keep the UI clean and uncluttered by not showing visual feedback unless you are adding value that is not available elsewhere.
Contact visualizations are especially critical for touch interactions that require accuracy and precision.
For example, your app should clearly indicate the location of a tap to после авиаперелета бессоница a user know if they missed their target, how much they missed it by, and what adjustments they must make.
Using the default XAML platform controls available ensures that your app works correctly on all devices and in all input situations.
If после авиаперелета бессоница app features custom interactions that require customized feedback, you should ensure the feedback is appropriate, spans input devices, and doesn't distract a user from their task. This can be a particular issue in game or drawing apps, where the visual feedback might conflict with or obscure critical UI.
We don't recommend changing the interaction behavior of the built-in gestures.
Feedback Across Devices
Visual feedback is generally dependent on the input device (touch, touchpad, mouse, pen/stylus, keyboard, and so on).
For example, the built-in feedback for a mouse usually involves moving and changing the cursor, while touch and pen require contact visualizations, and keyboard input and navigation uses focus rectangles and highlighting.
Use ShowGestureFeedback to set после авиаперелета бессоница behavior for the platform gestures.
If customizing feedback UI, ensure you provide feedback that supports, and is suitable for, all после авиаперелета бессоница modes.
Here are some examples of built-in contact visualizations in Windows.
All Windows apps sport a more defined focus после авиаперелета бессоница around interactable controls within the application.
These new focus visuals are fully customizable as well as disableable when needed.
There are two parts to the high visibility focus visuals: the primary border and the secondary border.
The primary border после авиаперелета бессоница 2px thick, and runs around the outside of the после авиаперелета бессоница border. The secondary border is 1px thick and runs после авиаперелета бессоница the inside of после авиаперелета бессоница primary border.
To change the thickness of either border type (primary or secondary) use the FocusVisualPrimaryThickness or FocusVisualSecondaryThickness, respectively:
The margin is a property of type Thickness, and therefore the margin can be customized to appear only on certain sides of the control.
The margin is the space between the control's visual bounds and the start of the focus visuals secondary border.
The default margin is 1px away from the control bounds.
You can edit this margin on a per-control basis, by changing the FocusVisualMargin property:
A negative margin will push the border away from the center после авиаперелета бессоница the control, and a positive margin will move the border closer to the center of the control.
To turn off focus visuals on the control entirely, simply disabled UseSystemFocusVisuals:
The thickness, margin, or whether or not после авиаперелета бессоница app-developer wishes to have the focus visuals at all, is determined on a per-control basis.
There are only two color properties for the focus visuals: the primary border color, and the secondary border color.
These focus visual border после авиаперелета бессоница can be changed per-control on an page level, and globally on an app-wide level:
To brand focus visuals app-wide, override the system brushes:
To change the colors on a per-control basis, just edit the focus visual properties on the desired control: