Raising event in another form

Question

Hi

I'm a bit new to custom events and delegates so I'm having problem to get a good solution to this problem.

I've got an MDI app that can load several forms as child-forms, all with different contents.

It can also show a .showdialog form for input of new data and on exiting this form the MDI form needs to notify one of the loaded Child forms that it's data has been changed and its time to reload the list content.

So, How can I raise an Event in one loaded Child form from the MDI form?

I can use something similar to this function to find out IF the child form is loaded or not.
(I'm using this function to avoid loading the same child form twice)

public static bool ShowThisChildWindow(String WinTagName)
{
      foreach (Form childForm in Application.OpenForms)
      {
         if (childForm.Tag != null)
         {
            if (childForm.Tag.ToString() == WinTagName.ToString())
            {
                childForm.BringToFront();
                return true;
            }
         }
       }
   return false;
}

Best Regards

Kjell

Vulpes · Answer

Well you have to define a suitable event (depending on what arguments you need to pass) an eventhandler on the MDI child form needs to subscribe to that event and the event then needs to be fired so that it will notify all subscribers. Suppose for example you defined this custom event in the MDI parent using the built-in EventHandler delegate type: public event EventHandler Notify; and you defined this method to fire it: public void OnNotify(object sender EventArgs e) { if (Notify != null) // i.e. there are some subscribers { Notify(sender e); // notify all subscribers } } and you also defined this eventhandler on the MDI Child form(s) to be notified: public void NotifyHandler(object sender EventArgs e) { // do stuff to reload the list content } When the MDI child is created from (presumably) the MDI parent it could then subscribe to this event: Form2 child = new Form2(); child.MdiParent = this; this.Notify += child.NotifyHandler; child.Show(); You could then fire the event from the MDI parent as follows: this.OnNotify(this EventArgs.Empty); and the NotifyHandler method on the child form will then get called automatically.

Kjell Liljegren · Answer

thanks Vulpes this is what I was looking for. Together with an article I found in another forum I managed to solve this problem by using a custom event. For anyone still having problem like I did to understand the basics of a custom event this article helped me: http://www.dreamincode.net/forums/topic/176796-quick-and-easy-custom-events/ To sumarize my solution based on the input Create the Event handler in the MDI-form -when instanciating a MDI-child let that new Child subscribe on the 'Event' You can then from the MDI raise the Event and the declared event function in the MDI-child will set off Rgds Kjell

Sam Hobbs · Answer

A form is not a document. In the past when Microsoft designed Windows and C++ was not yet a standard Microsoft designed MDI in a somewhat of an object-oriented way to store data as an object and provide a corresponding UI for it. The basic concept has been improved tremendously since then. Your design could be less complex if you were to think in terms of documents (objects) instead of thinking in terms of forms. MDI forms might be the most convenient solution but it is likely there are more appropriate solutions. If MDI is the most convenient solution then I will try to help you but I suspect that Vulpes will provide the assistance you want. Note that in my opinion a more object-oriented solution would make the application less complex.

Kjell Liljegren · Answer

Thank you both for inputs on this subject. firstly I do not think I have misunderstand the concept of MDI versus not MDI (SDI) i think its more of a language barrier My child forms can be called documents I mean; what is a document for some its a paper on the desk for other its a file and in this case it can be a form. So I have a MDI type of window application this app has some modules represented as Child forms meaning that the MDI-form is the MDIparent etc I hope this is in line with a MDI-application. Each of these child forms can only appear in one instance for controling this I gave each a unique TAG-property so if you try to load a second the for-mentioned function will find the first instance and bring that to the front for the user. One of these child forms has a list of objects and to add more of these objects I created a dialog form I dialog form for me is a .Showdialog type of form and this will force the user to respond to that dialog in order to proceed. and this is where my problem arises when the dialog finishes I can evaluate what took place in the dialog did the user Cancel it or fill it with information.... If it got filled I have a SP (Stored Procedure) that will create the new object and now we need to highlight to the Child form holding the list that it is one object short. This can be achived in many ways (i hope) but I would like if its possible to find a mechanism so i can raise an Event within that form so the Child Form itself re-runs the routine that fills the list with objects. The routine is already in place the user can either hit F5 or pull down a menu and choose Update List content So My problem is that the Function calling the .showdialog is within the MDI form hence the need to raise an event in another form not the MDI-form not the dialog form a completely different form that might not even be loaded. I can loop all loaded forms and find my form but how can I raise an event within that form? Kjell

Vulpes · Answer

I'm probably missing something here but it sounds as though all your child forms really need is a public or internal Notify() method which can be called from the parent form to tell them its time to reload the list content. If all the child forms were subscribing to some event then when the event was fired they'd all be notified simultaneously which doesn't sound like what you want unless they need to know when something is happening on one of the other children.

Sam Hobbs · Answer

It is likely that there is a better way to do what you need to do. Note that MDI means Multiple Document Interface. It is not designed for the purpose of showing multiple windows it is designed for multiple documents and a UI for each document. The UI includes a window and a menu. So when you say the MDI form needs to notify one of the loaded Child forms that it's data has been changed it sounds like you have data (called a document) corresponding with each child window. That is good. Hopefully it is just a matter of designing your application to be consistent with the way that MDI is designed to be used. So normally each child would process a request (show a dialog) for new data. The data should be stored in an object (the document) and then the window should be updated from the document. Does that sound relevant to your application?