When I use the MouseUp
event, I can get it to fire with a mouse right-click. But MouseLeftButtonUp
won\'t fire with either click!
Button
is using the Mouse[Left/Right]Button[Up/Down] events (and marking them as Handled
) for its Button.Click
events.
As Jobi said, you can use the PreviewMouseLeftButtonUp
event, but I want to suggest that you create your own button template and modify its behavior. (i.e. not mark the MouseLeftButtonUp
as Handled = true
) or simply use something else than a Button
as your parent container (depends on what you really need it for).
Looks like Button
control is eating up that event Since Button.Click
is actually a combination of LeftButtonDown
event and LeftButtonUp
event.
But you can subscribe to the tunneled event PreviewMouseLeftButtonUp
on the Button
instead of LeftButtonUp
.
Subscribing to a tunneled event instead of a bubble one has some pretty messy side effects which I will explain later.
Here is a better solution as in it keeps your bubble intact. :)
btnNewConfig.AddHandler(MouseLeftButtonUpEvent,
new RoutedEventHandler(btnNewConfig_MouseUp),
true);
You will have to declare your event handler with RoutedEventArgs
instead of MouseButtonEventArgs
but you can just cast it back to MouseButtonEventArgs
inside.
void btnNewConfig_MouseUp(object sender, RoutedEventArgs e)
{
MouseButtonEventArgs args = e as MouseButtonEventArgs;
// ...
}
Note the last argument in AddHandler
- making it true causes your event to fire even if previous handler set e.Handled = true;
Now about PreviewMouseLeftButtonUp
:
Tunneling events fire for parents before children. Bubbling - the opposite. If you have many event handlers involved you should really stick to all bubbling or all tunneling or else the more event handlers you add the more confusing it gets - adding one new event handler may cause you to revisit all the other ones in the application.
Most people find bubbling model a much more natural one. This is why the accepted answer is problematic.