You could for example pass a reference to your tool bar or your main form to
your user control when you create it. This way, your user control could
modify it itself. You could also have a look at the Parent property of your
user control. You could maybe do something with that.

However, i would rather not try to modify a user control's container from
the user control. This would break your code if you want latter to use your
module in another application that has a different user interface. My
approach would be to have a manager class in charge of creating of managing
all your modules (this manager class could be simply your main form class).
This manager class would be in charge of modifying your tool bar in regards
to which module is displayed. If a module needs to modify your main form's
menus, tool bars or status bar at some stage, expose events in your module.
The manager will subscribe to those events and handle the main form UI
modification itself. This way, your modules will be totally independant from
where and how they are placed and used. This will also make your code much
more readable as it will be clearly sperarated into different independant
components.

Hi !

Sorry for my late reply. I'm on vacation, and have to sneak in to my computer after my better half
is asleep and at odd days :)

Anyway, I belive the answer to that is yes. If you look at the article, they build a menu up from
scratch when you select the "grid thingy". You can control this stuff in the baseclass or in the
inherited or both. Aka - the framework lets you control which menus, toolbars are visible through
the "register" functions embedded.

I found that I've lost too much control, and decided to use the framework itself, but take controls
of navigation and menus outside of the framework. Anyway, I've got it working and timesaving when
you want to make new forms and load them into the same panel.

BTW - to access a module's public function you'll have to write something like this:

((modModCust)ModuleInfoCollection.Instance[2].Module).PrintScheme();

I've also put in the following code in the "basemodule" so I can reach the mainform (parent) from
any inherited module. (module = usercontrol):
MainForm = ((frmMain)this.FindForm());  // points back to the mother of all form (or usercontrols)
// (or modules)

That way, I can forinstance say something like this from any module.
MainForm.ShowEditButtons();

Best wishes
Kai Bohli
kaiboeNO_SPAM@online.no
Norway