Occurs when the mouse pointer leaves the boundaries of an element.
Assembly: PresentationCore (in PresentationCore.dll)
XMLNS for XAML: http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/netfx/2007/xaml/presentation
See [%$TOPIC/ms523144_en-us_VS_110_1_0_0_0_0%], [%$TOPIC/ms523144_en-us_VS_110_1_0_0_0_1%]
See [%$TOPIC/ms523144_en-us_VS_110_1_0_1_0_0%], [%$TOPIC/ms523144_en-us_VS_110_1_0_1_0_1%]
See [%$TOPIC/ms523144_en-us_VS_110_1_0_2_0_0%], [%$TOPIC/ms523144_en-us_VS_110_1_0_2_0_1%]
See [%$TOPIC/ms523144_en-us_VS_110_1_0_3_0_0%], [%$TOPIC/ms523144_en-us_VS_110_1_0_3_0_1%]
<object Mouse.MouseLeave="[%$TOPIC/ms523144_en-us_VS_110_1_0_4_0_0%]" .../>
This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see Attached Events Overview.
This event uses the direct event handling routing strategy. Direct routed events do not follow a route (they are only handled in the same element on which they are raised). They do, however, enable other aspects of routed event behaviors, such as event triggers in styles.
Although this event is used to track when the mouse leaves an element, it is also reporting that the IsMouseOver property value has changed from true to false on this element.
Routed Event Information
Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.