Occurs when a pointer that made contact abnormally loses contact.
Some of the reasons why you might get a PointerCanceled occurrence are:
- 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 logs off or similar interruptions that aren't app-specific
- The number of simultaneous contacts exceeded the number supported by the device
Note PointerCanceled might fire instead of PointerReleased. 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 the possible conclusions to a Press action, and that includes PointerCanceled.
When handling a PointerCanceled event, anticipate that some of the event data normally available for a pointer event won't be meaningful in the PointerRoutedEventArgs object you get through your handler. For example, the Position of the pointer is invalid because the pointer no longer exists.
PointerCanceled is a routed event. For more info on the routed event concept, see Events and routed events overview.
Minimum supported client
Minimum supported server
|Windows Server 2012|
Minimum supported phone
|Windows Phone 8.1 [Windows Runtime apps only]|
- Quickstart: Touch input
- Hit testing and input events
- XAML user input events sample