Question

Day 2 and I don’t have a clue. [.Net 3.5, VS 2008]

I have a UserControl that defines a ClickEvent:

public static readonly RoutedEvent ClickEvent = EventManager.RegisterRoutedEvent (
  "Click", RoutingStrategy.Bubble, typeof ( RoutedEventHandler ), typeof ( TouchToggleButton ) );

and an OnClick method:

protected virtual void OnClick ( )
{
    RaiseEvent ( new RoutedEventArgs { RoutedEvent = ClickEvent, Source = this } );
}

In each of two different windows, I wire an instance of this control to an event handler.

<wft:TouchToggleButton DockPanel.Dock="Top" x:Name="measurableButton" Click="measurableButton_Click">Cannot Measure</wft:TouchToggleButton>

and

<wft:TouchToggleButton x:FieldModifier="public" x:Name="BuyoutButton" Click="BuyoutButton_Click">Buyout</wft:TouchToggleButton>

and, finally, I have the two handlers defined:

private void measurableButton_Click ( object sender, RoutedEventArgs e )
{
    IsMeasurable = !IsMeasurable;
    OnMeasurableButtonChanged ( );
}

and

private void BuyoutButton_Click ( object sender, RoutedEventArgs e )
{
    IsBuyout = !IsBuyout;
    OnBuyoutButtonChanged ( );
}

In both cases, if I put a breakpoint at the OnClick, it hits. In the case of the measurableButton, the RaiseEvent goes to measurableButton_Click; in the case of the BuyoutButton, the RaiseEvent does NOT go to BuyoutButton_Click.

There is nowhere in the app an unwiring (-=) of the BuyoutButton.Click. What further could I check to discover the reason for the difference in these behaviors?

Answer 1

With thanks to Rachel for making me think about the event, I realized I had left out

public event RoutedEventHandler Click
{
    add { AddHandler ( ClickEvent, value ); }
    remove { RemoveHandler ( ClickEvent, value ); }
}

in my inherited class. (Being an event, it does not inherit.) This fixed my problem, although I still wonder how it ever worked in the first place.