Creating an Event for Objects...

Do I just create snippet that looks like this?

        private void Update_DataChanged(object sender, EventArgs e)
        {

        }

you can type in your own method name in the name field of the event

or you can just put a call to your method with in their stubbed in event.

So in the method I create - it appears I can't just create a:

private void Update_DataChanged()
{
     DataChanged = true;
}

I actually need to make it -

        private void Update_DataChanged(object sender, EventArgs e)
        {
             DataChanged = true;
        }


What does having the object sender, EventArgs e do that makes it available as a selection in the event list?

its the default delegate signature for parameters.

if you don't want to change that -- just call your method from the stubbed in event.

If it's always the same method... have them all relate to the same delegate handler method, then have that method tell yours to execute.  Not just accomplished by the designer, you will have to go into your designer code and modify it yourself, or add the events outside of the designer in the other code window for VS Windows Forms layouts.  Simply put, like the following. (is not full code but the gist of the idea)

>> What does having the object sender, EventArgs e do that makes it available as a selection in the event list?

Sorry, when I posted I didn't see any responses yet.

The signature you're referring to is the default signature for event-handling methods (not all methods, of course...). The "sender" object is (according to .NET standards) the object that fired the event. It provides a way to detect what fired the event without having separate methods for each and every object that may trigger the same code.

The second parameter, EventArgs, is an object that derives from the "EventArgs" class (or an instance of the EventArgs class itself). Meaningful data may or may not be passed, completely dependent on the event that was triggered. For example, a MouseClick event takes a MouseEventArgs parameter instead of EventArgs. The MouseEventArgs, which derives from EventArgs, holds data correpsonding to where the mouse was when it was clicked, which button(s) were clicked, etc. For methods that don't need this kind of data about their event, EventArgs.Empty is usually passed (again, according to .NET standard), instead of just null.

TextBox tbx1 = new TextBox();
TextBox tbx2 = new TextBox();

Constructor()
{
      tbx1.TextChanged += MyEvent;
      tbx2.TextChanged += MyEvent;
}

void MyEvent(Object sender, EventArgs e)
{
      YourMethodHere();
}

Sounds like your coming from the old VB style where the function name directly tied to the event handler.  In C# you "subscribe" your event handler function to the events of the particular control.  A control can therefore send the event to 0 or more handlers.  As long as the parameters of the handler function match what the control event can send out your set!  name is arbitrary.

An example of something I just did : i have a label that when compiled under debugging acts like a button (toggles some behind the scenes attributes for testing)   As you see a single or double click both activate the same event handler function.

this.label1.DoubleClick += new System.EventHandler(this.label1_Click);
this.label1.Click += new System.EventHandler(this.label1_Click);

                                              

1:
2:

Double click on the FIRST TextBox so you get the stub and add the code in there:

        private bool DataChanged = false;

        private void textBox1_TextChanged(object sender, EventArgs e)
        {
            DataChanged = true;
        }

Now go back to the Form design view and select all the rest of the TextBoxes.  Click on the Lightning bolt to get the events.  Find the TextChanged() event, click on the dropdown, and select "textBox1_TextChanged".

Now all of the TextBoxes will cause that same method to fire and thus toggle DataChanged to true.