getting OnPaint to fire

[Ron Vecchi]

I have a custyom control that has a property which wraps a collection. When
I add controls to the collection the OnPaint method of these newly added
controls never get fired.
But if I take the controls in the collection and add them to the custom
controls ControlCollecti on the OnPaint method is called.

I would like to use my Collection property but It seems that the controls
need to be added to the ControlCollecti on for them to work.
In my custom controls on paint method I loop through the Collection and add
them to the ControlCollecti on so the OnPaint will be called.

I'm pretty new to this, just wondering if this is an ass backwards way to
do this. Seems like it is and that I am missing something.
--------------------------------------

// myothercontrol OnPaint is never called from below example
MyCustomControl .CollectionPreo perty.Add(myoth ercontrol);

------------------------------------------------
////
// MyCustomControl OnPaint Method
// OnPaint menthod will get fired by using below example.
//

protected void OnPaint(PaintEv entArgs pe){
foreach(MyCusto mControl in this.Collection Property){
this.Controls.A dd(MyCustomCont rol);
}
}
--------------------------------
I was thinking that in the set and get accessor for the Collection Property
I could just get and set directly to the ControlCollecti on
but it still seems like I am wrong in my organization and thinking on this.
Any Insights?
--
Ron Vecchi

[Jeffrey Tan[MSFT]]

Hi Ron,

Thanks for posting in this group.
Based on my understanding, you find that the only the custom control's
Controls.Add method can make the child controls OnPaint method gets called.
I think this is by the design of .Net, Control.Control s.Add method does
many internal works.
So I think you should use the default ControlCollecti on of your custom
control.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Charlie Williams]

Oops, I clicked new post.

See my post titled "Why Not Both?"

Charlie

-----Original Message-----
I have a custyom control that has a property which wraps a collection. WhenI add controls to the collection the OnPaint method of these newly addedcontrols never get fired.
But if I take the controls in the collection and add them to the customcontrols ControlCollecti on the OnPaint method is called.

I would like to use my Collection property but It seems that the controlsneed to be added to the ControlCollecti on for them to work.In my custom controls on paint method I loop through the Collection and addthem to the ControlCollecti on so the OnPaint will be called.
I'm pretty new to this, just wondering if this is an ass backwards way todo this. Seems like it is and that I am missing something.--------------------------------------

// myothercontrol OnPaint is never called from below exampleMyCustomContro l.CollectionPre operty.Add(myot hercontrol);

------------------------------------------------
////
// MyCustomControl OnPaint Method
// OnPaint menthod will get fired by using below example.
//

protected void OnPaint(PaintEv entArgs pe){
foreach(MyCusto mControl in this.Collection Property){
this.Controls.A dd(MyCustomCont rol);
}
}
--------------------------------
I was thinking that in the set and get accessor for the Collection PropertyI could just get and set directly to the ControlCollecti onbut it still seems like I am wrong in my organization and thinking on this.

Any Insights?
--
Ron Vecchi

.

[Nicholas Paldino [.NET/C# MVP]]

Jeffrey,

I am curious, couldn't the original poster just call Invalidate on the
parent hosting the controls, which will in turn cause the parent and the
child controls (including the ones just added) to repaint correctly?

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

""Jeffrey Tan[MSFT]"" <v-*****@online.mi crosoft.com> wrote in message
news:rl******** ******@cpmsftng xa07.phx.gbl...

Hi Ron,

Thanks for posting in this group.
Based on my understanding, you find that the only the custom control's
Controls.Add method can make the child controls OnPaint method gets called. I think this is by the design of .Net, Control.Control s.Add method does
many internal works.
So I think you should use the default ControlCollecti on of your custom
control.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Casey Leamon]

As long as the custom control's onPaint is properly overriden, Invalidate()
should do exactly what you're looking for Ron.
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in
message news:uJ******** ******@TK2MSFTN GP12.phx.gbl...

Jeffrey,

I am curious, couldn't the original poster just call Invalidate on the
parent hosting the controls, which will in turn cause the parent and the
child controls (including the ones just added) to repaint correctly?

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

""Jeffrey Tan[MSFT]"" <v-*****@online.mi crosoft.com> wrote in message
news:rl******** ******@cpmsftng xa07.phx.gbl...

Hi Ron,

Thanks for posting in this group.
Based on my understanding, you find that the only the custom control's
Controls.Add method can make the child controls OnPaint method gets

called.

I think this is by the design of .Net, Control.Control s.Add method does
many internal works.
So I think you should use the default ControlCollecti on of your custom
control.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Jeffrey Tan[MSFT]]

Hi Nicholas,

Yes, Invalidate method will explicit force the control to repaint. So you
can also do this instead.
But I think the control's default controlcollecti on property is more
convinient to use. And it should meet your need.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.