Application architecture help needed

[Eddie Pazz]

Hi, I'm doing the proof of concept for a very large application. My initial
design shows the app exe file will probably hit about 2MG. I decided to
split the GUI into DLL to support the main form. My problem is as follows:

MyDLL contains a user control, MyUserList, that it's placed inside a
container in the MainForm. The app exe obviously has a reference to MyDLL so
it can find the control and load it.

What I need is a way for MyDLL.MyUserList to notify the MainForm when an
event occurs. For example, if the user selects multiple items, I want the
MainForm to update the toolbar accordingly. This is where I'm stumped.

How do I make the DLL notify the mainform of events? Circular references are
not allowed.

Any help would be appreciated. Thanks.

BTW, I tried placing a MDIChild form in the DLL and use the ChildActivate
event, but my design allows for only one View to be displayed at a time.
Multiple forms would be unnecessary. Besides, it seems that I can't get rid
of the Minimize/Maximize buttons in the child window without some funky hack
and a weird side effect when the form loads. Not acceptable.

Eddie.

[Kohinoor Basu]

Raise an event from the user control and sink into that event in your
main form.

Kohinoor.

Eddie Pazz wrote:

Hi, I'm doing the proof of concept for a very large application. My initial
design shows the app exe file will probably hit about 2MG. I decided to
split the GUI into DLL to support the main form. My problem is as follows:

MyDLL contains a user control, MyUserList, that it's placed inside a
container in the MainForm. The app exe obviously has a reference to MyDLL so
it can find the control and load it.

What I need is a way for MyDLL.MyUserList to notify the MainForm when an
event occurs. For example, if the user selects multiple items, I want the
MainForm to update the toolbar accordingly. This is where I'm stumped.

How do I make the DLL notify the mainform of events? Circular references are
not allowed.

Any help would be appreciated. Thanks.

BTW, I tried placing a MDIChild form in the DLL and use the ChildActivate
event, but my design allows for only one View to be displayed at a time.
Multiple forms would be unnecessary. Besides, it seems that I can't get rid
of the Minimize/Maximize buttons in the child window without some funky hack
and a weird side effect when the form loads. Not acceptable.

Eddie.