Ah, okay, from the designer. As far as I know the designer doesn't
support changing properties from the base class unless they're properties
of the base class. If you make the ToolStrip a virtual property of the
base class the derived class can edit it in the Designer; but only as a
property, you can't click on it and change properties. You have to click
on the control and expand the property to change the properties of that
child control. Example, in the base class add this property:
[Browsable(true)]
[EditorBrowsable(EditorBrowsableState.Always)]
[DesignerSerializationVisibility
(DesignerSerializationVisibility.Visible)]
public ToolStrip ToolStrip
{
get
{
return toolStrip1;
}
}
...and you will get a ToolStip property in the Properties grid, expanding
it you can change it's properties. Clicking on the toolstrip on the
control will show the it as the selected item but only read-only.
On Wed, 1 Aug 2007 16:07:15 -0500, Mike Andrews
<[EMAIL PROTECTED]> wrote:
>It's very odd.
>I draw a toolstrip control on a base usercontrol. I change the modifiers
>from private (yes, you're correct) to protected.
>I create a new user control and change the inheritance from UserControl to
>BaseUserControl (or whatever I've called it).
>I now cannot make any changes to that toolstrip control on the derived
>usercontrol, i.e., no context menu available and all properties in the
>properties window are disabled; I do, however, have access to the control
>via code.
>
>I created a test project outside of my main project just to see if this
>could be duplicated and it still does it in another project. I'm just at
a
>loss here.
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
