|
|
You're in the
dotnet windows forms
group:Why "GroupBox", "Panel" can contain other Controls ??
dotnet windows forms:
Are there any other "container" controls except "GroupBox" and "Panel" ? Thanks!
Hi Stan,
Basically all Controls can be containers as Control has a Controls property. You can put a button inside another button if you like. Or a TextBox that has Button with another TextBox inside of it. -- Happy coding!
Hi,
As you mentioned, I'v tried to get "Controls Property" from "Button" but I can find!? I'm not very clear about your concept. My scenario: 1.Put Button1 on form1; 2.Put Button2 over Button1; 3.User "Button2.Parent" to find Button2's parent; 4.I got "form1" , not "Button1"! If the same scenario but change "Button1" to "Panel1" then I'll get "Panel1" as Button2's parent. So if I want to make "Button1" as Button2's parent, how can I do? Thanks for your kind response! "Morten Wennevik" <MortenWennevik@hotmail.com> ??? news:op.sqcl31hnklbvpo@stone ???... [quoted text, click to view] > Hi Stan, property. You can put a button inside another button if you like. Or a> > Basically all Controls can be containers as Control has a Controls TextBox that has Button with another TextBox inside of it. [quoted text, click to view] > > > -- > Happy coding! > Morten Wennevik [C# MVP]
I'm not sure what you mean about cannot find the Controls property. However, it is not listed if you just search "Button." in the MSDN "Look For" list, you need to select the Control.
This sample should demonstrate putting a button inside another button. Button button1 = new Button(); button1.Text = "Button 1"; button1.Size = new Size(100, 100); form1.Controls.Add(button1); Button button2 = new Button(); button2.Text = "Button 2"; button1.Controls.Add(button2); button2.Click += new EventHandler(button2_Click); .... private void button2_Click(object sender, EventArgs e) { MessageBox.Show(((Button)sender).Parent.Text); } Note that if you just drag a button over another button in the Designer window, the designer won't actually put the button inside the other button but onto the underlying form. I suppose the designer assumes you don't want Button2 inside Button1. [quoted text, click to view] On Fri, 06 May 2005 14:33:25 +0200, Stan <jazz.stanley@msa.hinet.net> wrote: > Hi, > > As you mentioned, I'v tried to get "Controls Property" from "Button" but I > can find!? > I'm not very clear about your concept. > > My scenario: > > 1.Put Button1 on form1; > 2.Put Button2 over Button1; > 3.User "Button2.Parent" to find Button2's parent; > 4.I got "form1" , not "Button1"! > > If the same scenario but change "Button1" to "Panel1" then I'll get > "Panel1" as Button2's parent. > > So if I want to make "Button1" as Button2's parent, how can I do? > > Thanks for your kind response! > > > "Morten Wennevik" <MortenWennevik@hotmail.com> ??? > news:op.sqcl31hnklbvpo@stone ???... >> Hi Stan, >> >> Basically all Controls can be containers as Control has a Controls > property. You can put a button inside another button if you like. Or a > TextBox that has Button with another TextBox inside of it. >> >> >> -- >> Happy coding! >> Morten Wennevik [C# MVP] > > > -- Happy coding!
[quoted text, click to view]
> I suppose the designer assumes you don't want Button2 inside Button1. This is true. You must derive your control from ContainerControl if you want the designer to allow other controls to be dropped inside of yours. Like Morten said, all controls can contain Controls inside, the ContainerControl just offer additional layout functionality. -- Francisco Padron www.chartfx.com [quoted text, click to view] "Morten Wennevik" <MortenWennevik@hotmail.com> wrote in message news:op.sqcukd06klbvpo@stone... > I'm not sure what you mean about cannot find the Controls property. > However, it is not listed if you just search "Button." in the MSDN "Look > For" list, you need to select the Control. > > This sample should demonstrate putting a button inside another button. > > Button button1 = new Button(); > button1.Text = "Button 1"; > button1.Size = new Size(100, 100); > form1.Controls.Add(button1); > > Button button2 = new Button(); > button2.Text = "Button 2"; > button1.Controls.Add(button2); > button2.Click += new EventHandler(button2_Click); > > ... > > private void button2_Click(object sender, EventArgs e) > { > MessageBox.Show(((Button)sender).Parent.Text); > } > > Note that if you just drag a button over another button in the Designer > window, the designer won't actually put the button inside the other button > but onto the underlying form. I suppose the designer assumes you don't > want Button2 inside Button1. > > > > On Fri, 06 May 2005 14:33:25 +0200, Stan <jazz.stanley@msa.hinet.net> > wrote: > >> Hi, >> >> As you mentioned, I'v tried to get "Controls Property" from "Button" but >> I >> can find!? >> I'm not very clear about your concept. >> >> My scenario: >> >> 1.Put Button1 on form1; >> 2.Put Button2 over Button1; >> 3.User "Button2.Parent" to find Button2's parent; >> 4.I got "form1" , not "Button1"! >> >> If the same scenario but change "Button1" to "Panel1" then I'll get >> "Panel1" as Button2's parent. >> >> So if I want to make "Button1" as Button2's parent, how can I do? >> >> Thanks for your kind response! >> >> >> "Morten Wennevik" <MortenWennevik@hotmail.com> ??? >> news:op.sqcl31hnklbvpo@stone ???... >>> Hi Stan, >>> >>> Basically all Controls can be containers as Control has a Controls >> property. You can put a button inside another button if you like. Or a >> TextBox that has Button with another TextBox inside of it. >>> >>> >>> -- >>> Happy coding! >>> Morten Wennevik [C# MVP] >> >> >> > > > > -- > Happy coding! > Morten Wennevik [C# MVP]
All controls can parent another control. However the design time support is
available only for few of them. I'm not sure that the suggestion you've got, to inherit from ContainerControl, will help you in this matter. What you need to do is to create your own designer that inherits from ParentControlDesigner and attach this designer to that control of yours. HTH Stoitcho Goutsev (100) [C# MVP] [quoted text, click to view] "Stan" <jazz.stanley@msa.hinet.net> wrote in message news:eL8n2xfUFHA.1152@tk2msftngp13.phx.gbl... > How to see if the control is a "container" control ? > > Are there any other "container" controls except "GroupBox" and "Panel" ? > > Thanks! > >
Deriving from ContainerControl is enough to allow the designer to drop other
controls inside of your control. By deriving from ContainerControl you are automatically attaching a ScrollableControlDesigner to your control. ScrollableControlDesigner derives from ParentControlDesigner. So you are basically doing the same thing (in regards to this topic). One important point that Stoitcho brought is that having a designer that derives from ParentControlDesigner is what makes it work (not the fact that you derive from ContainerControl), so if you have a custom designer you MUST derive it from ParentControlDesigner. -- Francisco Padron www.chartfx.com
Francisco,
I agree that via inheriting from ContainerControl we add the design time functionality for hosting other control from the toolbox, However ScorllableControlDesigner is not good enough. It doesn't draw the border of the control, so the control is not visible unless DrawGrid is set to *false*. It is better in this case to inherit from Panel class. The only things Panel's designer does is to add that piece of code that draws the border if the panel doesn't have its own. However, I believe if one wants to create a new container control with design support one must want to have something more that already provided functionality. This is the major reason for me to believe that inhertiting from ContainerControl is not what Stan was after. Stoitcho Goutsev (100) [C# MVP] [quoted text, click to view] "Francisco Padron" <noreply@softwarefx.com> wrote in message news:O1xWMzmVFHA.1148@tk2msftngp13.phx.gbl... > Deriving from ContainerControl is enough to allow the designer to drop > other controls inside of your control. > > By deriving from ContainerControl you are automatically attaching a > ScrollableControlDesigner to your control. ScrollableControlDesigner > derives from ParentControlDesigner. So you are basically doing the same > thing (in regards to this topic). > > One important point that Stoitcho brought is that having a designer that > derives from ParentControlDesigner is what makes it work (not the fact > that you derive from ContainerControl), so if you have a custom designer > you MUST derive it from ParentControlDesigner. > > -- > Francisco Padron > www.chartfx.com >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |