MouseGesture Class


The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

Defines a mouse input gesture that can be used to invoke a command.

Namespace:   System.Windows.Input
Assembly:  PresentationCore (in PresentationCore.dll)


public class MouseGesture : InputGesture


Initializes a new instance of the MouseGesture class.


Initializes a new instance of the MouseGesture class using the specified MouseAction.

System_CAPS_pubmethodMouseGesture(MouseAction, ModifierKeys)

Initializes a new instance of the MouseGesture class using the specified MouseAction and ModifierKeys.


Gets or sets the modifier keys associated with this MouseGesture.


Gets or sets the MouseAction associated with this gesture.


Determines whether the specified object is equal to the current object.(Inherited from Object.)


Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)


Serves as the default hash function. (Inherited from Object.)


Gets the Type of the current instance.(Inherited from Object.)

System_CAPS_pubmethodMatches(Object, InputEventArgs)

Determines whether MouseGesture matches the input associated with the specified InputEventArgs object.(Overrides InputGesture.Matches(Object, InputEventArgs).)


Creates a shallow copy of the current Object.(Inherited from Object.)


Returns a string that represents the current object.(Inherited from Object.)

Unlike a KeyGesture, a MouseAction does not have to be paired with ModifierKeys to be a valid MouseGesture.

A MouseGesture can be bound to a RoutedCommand (or other ICommand implementations) through a MouseBinding so that the command is invoked when the MouseGesture occurs.

For MouseGesture XAML attribute usages, the property that is generally set in XAML is Gesture, in cases where the gesture can represent both a mouse action and one or more modifier key. You can also set the Gesture property to be just a mouse action. In general, it is recommended that you use only the Gesture attribute from XAML, rather than setting MouseAction, even if you do not specify modifiers. This will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.

MouseGesture XAML object element usages are possible but uncommon, because you can ordinarily set the Gesture property of MouseBinding inline without the use of property element syntax. 

<object property="mouseAction"/>
- or -
<object property="oneOrMoreModifierKeys+mouseAction"/>



A single mouse action.


One or more modifier keys, defined by the ModifierKeys enumeration. If more than one modifier key is provided, each modifier key is delimited with a "+" character.

The following example shows to create a MouseGesture and associate it with a RoutedCommand through a MouseBinding. When the mouse wheel is clicked while the Control key is pressed, the Open is invoked.

<MouseBinding Gesture="Control+WheelClick"
              Command="ApplicationCommands.Open" />
MouseGesture OpenCmdMouseGesture = new MouseGesture();
OpenCmdMouseGesture.MouseAction = MouseAction.WheelClick;
OpenCmdMouseGesture.Modifiers = ModifierKeys.Control;

MouseBinding OpenCmdMouseBinding = new MouseBinding();
OpenCmdMouseBinding.Gesture = OpenCmdMouseGesture;
OpenCmdMouseBinding.Command = ApplicationCommands.Open;


.NET Framework
Available since 3.0

Any public static ( Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Return to top