Firing your own events can be quite useful. There are many times in which doing so is the preferred method. For instance, when you load a dialog with saved data you may need to adjust the "Enabled" property for some of the controls based on the data. It is quite acceptable to fire off a control's event handler when you are loading to make sure that the controls are in the proper state. Plus, if you change something in that handler, it takes effect everywhere that you use it which makes management of the code easier.
...Glenn On Mon, Sep 29, 2008 at 4:29 PM, BJ <[EMAIL PROTECTED]> wrote: > > Kevin / Glenn, > > Thank you for the replies. I posted this question on another user > group and got slightly ripped by one of the posters. They wanted to > know why I was trying to manaully fire an Event that I didn't write > the Handler. Other then it seemed like a good idea at the time, I > could come up with an answer. But based on their response, fine ok, > I'll write my own Event, handel it, and fire it when I needed too. > > Some developers get soooo touching that way :-) > > -B > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx <p><a href="http://feeds.feedburner.com/DotNetDevelopment";><img src="http://feeds.feedburner.com/~fc/DotNetDevelopment?bg=99CCFF&fg=444444&anim=1"; height="26" width="88" style="border:0" alt="" /></a></p> -~----------~----~----~----~------~----~------~--~---
