|
|
You're in the
dotnet windows forms
group:OnClick from UserControl Button
dotnet windows forms:
Another dumb newbie question, sorry. I want to be able to create applications by dragging my own version of controls onto a Form. The reason for making say a button as a user control, is I want to button color to be a specific color and not the default color. When I drag the Usercontrol onto the form it all looks fine, but when it executes, the onclick can't be set on the usercontrol. I'm guessing the OnClick on the button needs to send an event to theUserControl so I can get at the onclick event in the designer. Is there a better way to do this? If this is the best way to do this, do I need to propergate all the possible actions of the control up to the UserControl? Thanks Dave
Hi Tim
I changed the class to be derived from Button instead of UserControl, but there are obviously some other things that need to be changed. Starting with a UserControl doesn't seem the best way, but the only other UI option seems to be a Form, so now I'm confussed! Any examples you know of that would explain the procedure to a dumbass newbie would be appreciated. Thanks Dave [quoted text, click to view] "Tim Wilson" wrote:
> So you just want to change the default color of a Button but allow this > control to be reusable from the ToolBox? If so, then you should derive your > control directly from the Button class and not from UserControl. > > -- > Tim Wilson > ..Net Compact Framework MVP > > "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message > news:93158DD8-A2CB-46AC-90E6-D75BFE04E7C3@microsoft.com... > > Hi There > > > > Another dumb newbie question, sorry. I want to be able to create > > applications by dragging my own version of controls onto a Form. The > reason > > for making say a button as a user control, is I want to button color to be > a > > specific color and not the default color. When I drag the Usercontrol onto > > the form it all looks fine, but when it executes, the onclick can't be set > on > > the usercontrol. I'm guessing the OnClick on the button needs to send an > > event to theUserControl so I can get at the onclick event in the designer. > > > > Is there a better way to do this? > > > > If this is the best way to do this, do I need to propergate all the > possible > > actions of the control up to the UserControl? > > > > Thanks > > Dave > > > >
So you just want to change the default color of a Button but allow this
control to be reusable from the ToolBox? If so, then you should derive your control directly from the Button class and not from UserControl. -- Tim Wilson ..Net Compact Framework MVP [quoted text, click to view] "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message news:93158DD8-A2CB-46AC-90E6-D75BFE04E7C3@microsoft.com... > Hi There > > Another dumb newbie question, sorry. I want to be able to create > applications by dragging my own version of controls onto a Form. The reason > for making say a button as a user control, is I want to button color to be a > specific color and not the default color. When I drag the Usercontrol onto > the form it all looks fine, but when it executes, the onclick can't be set on > the usercontrol. I'm guessing the OnClick on the button needs to send an > event to theUserControl so I can get at the onclick event in the designer. > > Is there a better way to do this? > > If this is the best way to do this, do I need to propergate all the possible > actions of the control up to the UserControl? > > Thanks > Dave >
A UserControl is a composite control. This means that the control is usually
exposed as other controls simply grouped together. So the reason that you have a designer view of the UserControl is to allow you to easily drag and drop controls from the ToolBox. In your case, you just want to modify the default behavior of a single control. So the best approach would be to just inherit directly from this control. The main benefit is that all the events and properties of the Button will be directly exposed through your custom control since they are inherited. The quick start tutorial, linked below, has some useful information on getting started building custom controls. http://samples.gotdotnet.com/quickstart/winforms/doc/WinFormsCreatingControls.aspx -- Tim Wilson ..Net Compact Framework MVP [quoted text, click to view] "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message news:3734BC9F-3504-4BBA-B828-2CEB42A6519D@microsoft.com... > Hi Tim > > I changed the class to be derived from Button instead of UserControl, but > there are obviously some other things that need to be changed. Starting with > a UserControl doesn't seem the best way, but the only other UI option seems > to be a Form, so now I'm confussed! Any examples you know of that would > explain the procedure to a dumbass newbie would be appreciated. > > Thanks > Dave > > > "Tim Wilson" wrote: > > > So you just want to change the default color of a Button but allow this > > control to be reusable from the ToolBox? If so, then you should derive your > > control directly from the Button class and not from UserControl. > > > > -- > > Tim Wilson > > ..Net Compact Framework MVP > > > > "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message > > news:93158DD8-A2CB-46AC-90E6-D75BFE04E7C3@microsoft.com... > > > Hi There > > > > > > Another dumb newbie question, sorry. I want to be able to create > > > applications by dragging my own version of controls onto a Form. The > > reason > > > for making say a button as a user control, is I want to button color to be > > a > > > specific color and not the default color. When I drag the Usercontrol onto > > > the form it all looks fine, but when it executes, the onclick can't be set > > on > > > the usercontrol. I'm guessing the OnClick on the button needs to send an > > > event to theUserControl so I can get at the onclick event in the designer. > > > > > > Is there a better way to do this? > > > > > > If this is the best way to do this, do I need to propergate all the > > possible > > > actions of the control up to the UserControl? > > > > > > Thanks > > > Dave > > > > > > > > >
Hi Tim
That was exactly what I needed! Thankyou You wouldn't be interested in looking at another thread I have going called "Form component like common Openfiledialog"? Thanks again Dave [quoted text, click to view] "Tim Wilson" wrote:
> A UserControl is a composite control. This means that the control is usually > exposed as other controls simply grouped together. So the reason that you > have a designer view of the UserControl is to allow you to easily drag and > drop controls from the ToolBox. In your case, you just want to modify the > default behavior of a single control. So the best approach would be to just > inherit directly from this control. The main benefit is that all the events > and properties of the Button will be directly exposed through your custom > control since they are inherited. The quick start tutorial, linked below, > has some useful information on getting started building custom controls. > http://samples.gotdotnet.com/quickstart/winforms/doc/WinFormsCreatingControls.aspx > > -- > Tim Wilson > ..Net Compact Framework MVP > > "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message > news:3734BC9F-3504-4BBA-B828-2CEB42A6519D@microsoft.com... > > Hi Tim > > > > I changed the class to be derived from Button instead of UserControl, but > > there are obviously some other things that need to be changed. Starting > with > > a UserControl doesn't seem the best way, but the only other UI option > seems > > to be a Form, so now I'm confussed! Any examples you know of that would > > explain the procedure to a dumbass newbie would be appreciated. > > > > Thanks > > Dave > > > > > > "Tim Wilson" wrote: > > > > > So you just want to change the default color of a Button but allow this > > > control to be reusable from the ToolBox? If so, then you should derive > your > > > control directly from the Button class and not from UserControl. > > > > > > -- > > > Tim Wilson > > > ..Net Compact Framework MVP > > > > > > "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message > > > news:93158DD8-A2CB-46AC-90E6-D75BFE04E7C3@microsoft.com... > > > > Hi There > > > > > > > > Another dumb newbie question, sorry. I want to be able to create > > > > applications by dragging my own version of controls onto a Form. The > > > reason > > > > for making say a button as a user control, is I want to button color > to be > > > a > > > > specific color and not the default color. When I drag the Usercontrol > onto > > > > the form it all looks fine, but when it executes, the onclick can't be > set > > > on > > > > the usercontrol. I'm guessing the OnClick on the button needs to send > an > > > > event to theUserControl so I can get at the onclick event in the > designer. > > > > > > > > Is there a better way to do this? > > > > > > > > If this is the best way to do this, do I need to propergate all the > > > possible > > > > actions of the control up to the UserControl? > > > > > > > > Thanks > > > > Dave > > > > > > > > > > > > > > >
Ok. I'll reply in that thread.
-- Tim Wilson ..Net Compact Framework MVP [quoted text, click to view] "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message news:C0B3614A-86D3-4889-9C48-31ABCDBCA944@microsoft.com... > Hi Tim > > That was exactly what I needed! Thankyou > > You wouldn't be interested in looking at another thread I have going called > "Form component like common Openfiledialog"? > > Thanks again > Dave > > "Tim Wilson" wrote: > > > A UserControl is a composite control. This means that the control is usually > > exposed as other controls simply grouped together. So the reason that you > > have a designer view of the UserControl is to allow you to easily drag and > > drop controls from the ToolBox. In your case, you just want to modify the > > default behavior of a single control. So the best approach would be to just > > inherit directly from this control. The main benefit is that all the events > > and properties of the Button will be directly exposed through your custom > > control since they are inherited. The quick start tutorial, linked below, > > has some useful information on getting started building custom controls. > > http://samples.gotdotnet.com/quickstart/winforms/doc/WinFormsCreatingControls.aspx > > > > -- > > Tim Wilson > > ..Net Compact Framework MVP > > > > "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message > > news:3734BC9F-3504-4BBA-B828-2CEB42A6519D@microsoft.com... > > > Hi Tim > > > > > > I changed the class to be derived from Button instead of UserControl, but > > > there are obviously some other things that need to be changed. Starting > > with > > > a UserControl doesn't seem the best way, but the only other UI option > > seems > > > to be a Form, so now I'm confussed! Any examples you know of that would > > > explain the procedure to a dumbass newbie would be appreciated. > > > > > > Thanks > > > Dave > > > > > > > > > "Tim Wilson" wrote: > > > > > > > So you just want to change the default color of a Button but allow this > > > > control to be reusable from the ToolBox? If so, then you should derive > > your > > > > control directly from the Button class and not from UserControl. > > > > > > > > -- > > > > Tim Wilson > > > > ..Net Compact Framework MVP > > > > > > > > "DiamondDave" <DiamondDave@discussions.microsoft.com> wrote in message > > > > news:93158DD8-A2CB-46AC-90E6-D75BFE04E7C3@microsoft.com... > > > > > Hi There > > > > > > > > > > Another dumb newbie question, sorry. I want to be able to create > > > > > applications by dragging my own version of controls onto a Form. The > > > > reason > > > > > for making say a button as a user control, is I want to button color > > to be > > > > a > > > > > specific color and not the default color. When I drag the Usercontrol > > onto > > > > > the form it all looks fine, but when it executes, the onclick can't be > > set > > > > on > > > > > the usercontrol. I'm guessing the OnClick on the button needs to send > > an > > > > > event to theUserControl so I can get at the onclick event in the > > designer. > > > > > > > > > > Is there a better way to do this? > > > > > > > > > > If this is the best way to do this, do I need to propergate all the > > > > possible > > > > > actions of the control up to the UserControl? > > > > > > > > > > Thanks > > > > > Dave > > > > > > > > > > > > > > > > > > > > > > >
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 |