UIElement.PointerReleased Event

public:
 virtual event PointerEventHandler ^ PointerReleased;

// Register
event_token PointerReleased(PointerEventHandler const& handler) const;

// Revoke with event_token
void PointerReleased(event_token const* cookie) const;

// Revoke with event_revoker
UIElement::PointerReleased_revoker PointerReleased(auto_revoke_t, PointerEventHandler const& handler) const;

public event PointerEventHandler PointerReleased;

function onPointerReleased(eventArgs) { /* Your code */ }
uIElement.addEventListener("pointerreleased", onPointerReleased);
uIElement.removeEventListener("pointerreleased", onPointerReleased);
- or -
uIElement.onpointerreleased = onPointerReleased;

Public Custom Event PointerReleased As PointerEventHandler 

<uiElement PointerReleased="eventhandler"/>

Event Type

Remarks

Touch, mouse, and pen/stylus interactions are received, processed, and managed as pointer input in an app. Any of these interactions can produce a PointerReleased event. For more info, see Handle pointer input.

Other events instead of PointerReleased may fire at the end of the action— for example, PointerCanceled or PointerCaptureLost. Don't rely on PointerPressed and PointerReleased events always occurring in pairs. To function properly, your app must listen for and handle all events that represent likely conclusions to the Press action. Some of the reasons why you might not get a PointerReleased occurrence are:

• Differences in how specific hardware handles touch actions and Press actions
• A programmatic pointer capture from a different pointer
• User actions that change the relationship of the display area, such as changing resolution or monitor settings
• Input interactions such as a stylus touching the same surface as a previous touch action

The user action that fires a PointerReleased event initially can result in the Tapped event, or can also result in RightTapped under conditions that vary per device. For more info, see Tapped and RightTapped.

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 PointerPressed event. The PointerReleased event is fired only when that same mouse button is released (no other button can be associated with the pointer until this event is complete). Because of this exclusive association, other mouse button clicks are routed through the PointerMoved event. You can test the mouse button state when handling this event, as shown in the following example.

PointerReleased is a routed event. For more info on the routed event concept, see Events and routed events overview.

For touch actions and also for interaction-specific or manipulation events that are consequences of a touch action, an element must be hit-test visible in order to be the event source and fire the event that is associated with the action. UIElement.Visibility must be Visible. Other properties of derived types also affect hit-test visibility. For more info, see Events and routed events overview.

PointerReleased supports the ability to attach event handlers to the route that will be invoked even if the event data for the event is marked Handled. See AddHandler.

Specific Windows Runtime controls may have class-based handling for the PointerReleased input event. If so, the control probably has an override for the method OnPointerReleased. Typically the event is marked handled by the class handler, and the PointerReleased event is not raised for handling by any user code handlers on that control. For more info on how class-based handling for events works, see Events and routed events overview.

Controls may also have a PointerUpThemeAnimation personality animation that run independently of the event.

Applies to

See also

• PointerRoutedEventArgs
• Tapped
• PointerPressed
• Handle pointer input
• Relative mouse movement and CoreWindow
• XAML user input events sample