🚀 go-pugleaf

> The question is where the "bug" really is - is it in VS 2005, or in the 
> nature of the controls? If that latter than Delphi probably won;t be able to 
> help since it will be providing the same  .Net 2.0 controls. If the former, 
> then it is certainly possible Delphi will be able to address this, but not 
> enough is known about Delphi 2007 (Highlander) yet to know if that is the 
> case.

Thanks for your answer. Even don't know where this bug is. You can read 
this:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=115264

I read there next:

------------------------------------------------------------------------

This is not the disability of the VS Designer but it is the ability of 
the CustomeDesigners available in VS 2005. For each complex control 
there is a CustomeDesigner, like for DataGridView there is a custome 
Designer name DataGridViewDesigner in System.Design.dll, which make the 
properties in the child class read only. So if you provide the 
ControlDesigner (which is the FATHER of all designers, and is capable to 
handle almost all the designing functionality) as the designer for any 
control then the problem will be solve.

-------------------------------------------------------------------------

I know that Borland has very big experience in visual inheritance since 
D2. I used this future in D6 and D7 and it worked excellent. So maybe 
your engineers can write own control designers. If you'll search 
discussing of this problem in internet you will find many people who 
need it...