Manipulation Started Event
// Register event_token ManipulationStarted(ManipulationStartedEventHandler const& handler) const; // Revoke with event_token void ManipulationStarted(event_token const* cookie) const; // Revoke with event_revoker ManipulationStarted_revoker ManipulationStarted(auto_revoke_t, ManipulationStartedEventHandler const& handler) const;
public event ManipulationStartedEventHandler ManipulationStarted;
Public Custom Event ManipulationStarted As ManipulationStartedEventHandler
For custom controls and interaction experiences, see GestureRecognizer.ManipulationStarted.
ManipulationStarted represents that the manipulation recognition logic has detected pointer movement. In this case it's the second manipulation event to fire in a typical sequence, firing after ManipulationStarting, but before ManipulationDelta or other events such as ManipulationInertiaStarting.
An element must have a ManipulationMode value other than None or System to be a manipulation event source. The default value of ManipulationMode is System, which enables built-in control logic to process manipulations, but doesn't permit app code to handle manipulation events. If you want to handle manipulations, set ManipulationMode to All, or to specific ManipulationModes values. For more info, see ManipulationMode.
ManipulationStarted is a routed event. If the event is permitted to bubble up to parent elements because it goes unhandled, then it is possible to handle the event on parent elements even if ManipulationMode is None or System on the parent element. 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.