Re: Inherited Form Problem
The reason that they are invisible is probably because they are on a ToolStripPanel (the top panel of the container) which is hidden (collapsed).
That said, you cannot edit any controls that are on the inherited base form anyway. You can only edit them in the base form, and those changes will then show up in all derived forms. That is just how inherited forms work.
I do find that, in the case of Menu/Toolstrips, this is not optimal behavior. I would like it if you could still have the option of adding items to them. I am often in a situation where I need many forms with the same layout, but other toolstrip items. I do however have an Infragistics toolset which has a new toolstrip control which I'm pretty sure is editable in inherited forms. I'm not sure how they did that, lol.
Re: Inherited Form Problem
What is the point of having a container in the base form if you can't add items to it in the inherited form?
Re: Inherited Form Problem
You need to add the items in the base form, so they must be the same in all inherited forms. At least, I have always thought that. Someone else may come along and tell us that that is not the case at all, but I'm pretty sure that I'm right :p
I don't think it's very good either, but we've gotta live with it.
Anyway, if it's just the one ToolStrip why not simply add it manually to all inherited forms? That would take half a second for each form.
Re: Inherited Form Problem
I've got a toolstrip with five buttons on it, all code behind them is the same so implemented on the base form. I just need to add some additional buttons (sometimes) on an inherited form. Having to duplicate that on every form completely undermines the point of inheritance. You're supposed to be able to indicate (with the 'Modifiers' property) whether a control should be modifiable in the inherited form.
Re: Inherited Form Problem