Disable a WPF button, but still swallow the click events

Question

I have a button in my application which is bound to a command. This button sits inside another control which also reacts to mouseclicks. When the button is enabled I get the behaviour that I expect - click on the button and the command is triggered, click outside the button but inside the container control and that is triggered instead.

Unfortunately when the button is disabled (through the CanExecute method of the command) the clicks on the button are bubbled up to the container control. I don't want this, I want the clicks to be swallowed - neither trigger the command nor bubble up.

I tried to overcome this by created a new class inheriting from Button but none of the following methods even seem to get called on a disabled button:

• OnPreviewMouseDown
• OnPreviewMouseUp
• OnPreviewMouseLeftButtonDown
• OnPreviewMouseLeftButtonUp
• OnMouseDown
• OnMouseUp
• OnMouseLeftButtonDown
• OnMouseLeftButtonUp
• OnClick

Is a disabled control completely ignored by the WPF routed event system? And if so is there anyway that I can get the behaviour that I'm looking for?

Answer 1

It isn't really clean, but you could put a transparent rectangle behind your button that swallows click events.

Answer 2

What you want to do is register a routed event handler using the overload that takes the handledEventsToo parameter and specifying a value of true for that parameter. This way your outer handler will receive the event regardless of whether or not the button actually handles the event. That will look something like this:

this.AddHandler(Mouse.MouseUpEvent, this.MyMouseUpHandler, true);

And then in your handler you can always check what was clicked, whether it was handled, etc. via the MouseButtonEventArgs you are handed. For example, to check if another control actually handled the event already you can do:

if(!args.Handled)
{
     // handle it here instead
}

Answer 3

RCGoforth's answer got me 90% of the way there, but the solution isn't to put a rectangle behind the button, because the bubbling event goes up the tree not across to siblings. In the end I surrounded the button with a ContentControl (since rectangle's can't have children) which swallowed the event before it could go up any further:

<ContentControl MouseDown="ContentControl_MouseDown">
    <Button Content="Click Test"
            Padding="2"
            Command="{Binding TestCommand}"/>
</ContentControl>

In the code behind:

private void ContentControl_MouseDown(object sender, MouseButtonEventArgs e)
{
    e.Handled = true;
}

---

Or to do this entirely in XAML (and to increase the hack level of the code...)

<Button>
    <Button.Template>
        <ControlTemplate>
            <Button Content="Click Test"
                    Command="{Binding TestCommand}"/>
        </ControlTemplate>
    </Button.Template>
</Button>

Answer 4

A cleaner, more reusable solution would be implement this functionality as an attached property.

Using the service/action pattern:

namespace Control.Services
{

  public class UIElementService
  {
    public static readonly DependencyProperty HandleMouseEventsProperty = DependencyProperty.RegisterAttached("HandleMouseEvents",
      typeof(bool), typeof(UIElementService), new FrameworkPropertyMetadata(false, UIElementService.HandleMouseEventsPropertyChanged));

    static void HandleMouseEventsPropertyChanged(object sender, DependencyPropertyChangedEventArgs e)
    {
      FrameworkElement element = sender as FrameworkElement;
      if (element == null)
        return;

      new HandleMouseEventsAction(element);
    }

    public static bool GetHandleMouseEvents(FrameworkElement target)
    {
      return (bool)target.GetValue(HandleMouseEventsProperty);
    }

    public static void SetHandleMouseEvents(FrameworkElement target, bool value)
    {
      target.SetValue(HandleMouseEventsProperty, value);
    }

    class HandleMouseEventsAction
    {
      UIElement m_Target;
      MouseButtonEventHandler m_Handler;

      internal HandleMouseEventsAction(FrameworkElement source)
      {
        m_Source = source;
        m_Handler = new MouseButtonEventHandler(PreviewMouseLeftButtonUp);

        m_Source.Loaded += OnSource_Loaded;
        m_Source.Unloaded += OnSource_Unloaded;
      }

      void OnSource_Loaded(object sender, RoutedEventArgs e)
      {
        m_Source.AddHandler(Mouse.PreviewMouseUpEvent, m_Handler, true);
      }

      void OnSource_Unloaded(object sender, RoutedEventArgs e)
      {
        m_Source.RemoveHandler(Mouse.PreviewMouseUpEvent, m_Handler);
      }

      void PreviewMouseLeftUIElementUp(object sender, MouseUIElementEventArgs e)
      {
        e.Handled = true;
      }

    }

  }

}

Then to use, import the namespace.

<Button sv:UIElementService.HandleMouseEvents="True" />

or

<ContentControl sv:UIElementService.HandleMouseEvents="True">
    <Button Content="Click Test" Padding="2" Command="{Binding TestCommand}"/>
</ContentControl>

I have not tested this (no time at the moment). I believe the action will still get the mouse events even if disabled.

HTH,

Dennis