Mouse.MouseUp 附加事件


当释放任何鼠标按钮时发生。Occurs when any mouse button is released.

see AddMouseUpHandler, and RemoveMouseUpHandler
see AddMouseUpHandler, and RemoveMouseUpHandler
see AddMouseUpHandler, and RemoveMouseUpHandler


已释放的鼠标按钮通过检查事件的参数来确定。Which mouse button was released is determined by checking the arguments of the event.

这是一个附加事件。This is an attached event. WPFWPF将附加事件作为路由事件实现。implements attached events as routed events. 附加事件本质上是XAMLXAML一种用于引用事件的语言概念, 这些事件可在未定义该事件的对象WPFWPF上进行处理, 后者通过同时启用事件来遍历路由。Attached events are fundamentally a XAMLXAML language concept for referencing events that can be handled on objects that do not define that event, which WPFWPF expands upon by also enabling the event to traverse a route. 附加事件在代码中没有直接处理语法;若要在代码中附加路由事件的处理程序, 请使用指定的 Add * 处理程序方法。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.

MouseRightButtonUp MouseLeftButtonUp UIElement 公共语言运行时 (CLR)common language runtime (CLR)此框架通过将其作为两个不同的事件呈现在上, 在此附加事件上生成: 和。 Windows Presentation Foundation (WPF)Windows Presentation Foundation (WPF)The Windows Presentation Foundation (WPF)Windows Presentation Foundation (WPF) framework builds on this attached event by surfacing it as two different 公共语言运行时 (CLR)common language runtime (CLR) events on UIElement: MouseLeftButtonUp and MouseRightButtonUp. 这些实现处理基础MouseUp事件并读取事件的参数, 以确定是否涉及鼠标左键或右键。These implementations handle the underlying MouseUp event and read the arguments of the event to determine whether the left or right mouse button was involved. 对于三按钮, 中间按钮没有框架级事件支持, 您应该使用MouseUp事件并检查事件参数中的中间按钮条件。For three-button, there is no framework-level event support for the center button, and you should use the MouseUp event and check for the center button condition in the event arguments.

对于与鼠标相关的路由事件, 请注意如何或何时将其标记为已处理。For routed events that relate to the mouse, be careful about how or when you mark them handled. 对父元素是否还应告知父元素是否还应知道是否应该知道是否有任何给定鼠标操作的难点是WPFWPF , 这是因为框架选择了将Mouse基础路由事件作为CLRCLR沿路由的所有事件。The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the WPFWPF framework chose the model of having the underlying Mouse routed event be surfaced as CLRCLR events all along the route.

隧道鼠标事件存在类似问题。Similar issues exist with tunneling mouse events. 是否应该处理事件, 而不是由进一步流向源的子级处理, 以及如何影响组合项可能具有预期的鼠标行为的控件中的组合?Should you handle the event and not have it be handled by children further towards the source, and how would that affect compositing in a control where the compositing pieces might have expected mouse behaviors?

路由事件信息Routed Event Information

标识符字段Identifier field MouseUpEvent
路由策略Routing strategy 冒泡Bubbling
委托Delegate MouseButtonEventHandler

对应的隧道事件为PreviewMouseUpThe corresponding tunneling event is PreviewMouseUp.