Occurs when an element captures the mouse.
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/ms523136_en-us_VS_110_1_0_0_0_0%], [%$TOPIC/ms523136_en-us_VS_110_1_0_0_0_1%]
See [%$TOPIC/ms523136_en-us_VS_110_1_0_1_0_0%], [%$TOPIC/ms523136_en-us_VS_110_1_0_1_0_1%]
See [%$TOPIC/ms523136_en-us_VS_110_1_0_2_0_0%], [%$TOPIC/ms523136_en-us_VS_110_1_0_2_0_1%]
See [%$TOPIC/ms523136_en-us_VS_110_1_0_3_0_0%], [%$TOPIC/ms523136_en-us_VS_110_1_0_3_0_1%]
<object Mouse.GotMouseCapture="[%$TOPIC/ms523136_en-us_VS_110_1_0_4_0_0%]" .../>
When an element captures the mouse, it receives mouse input whether or not the cursor is within its borders.
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.
Because of the bubbling routing, the actual element that has capture might be a child element, not necessarily the element where the event handler is actually attached. Check the Source in the event arguments to determine the actual element that has mouse capture.
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.