🚀 go-pugleaf

sasha wrote:
> 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.

It sounds like it would be possible to supply one's own designers to replace 
the ones supplied by MS, but of course this might be a lot of work too. So 
the question becomes whether that extra work is worth it. Yes, it would help 
some number of developers and be a something that could be trumpeted over 
VS, but would the cost really be returned in additional sales of the 
product? My *guess* is probably not and that the MS designers will be the 
ones used for MS controls.

By the wording in your reply, I need to also point out that TeamB members 
are not Borland/Codegear employees - we are customers just like you.

-- 
Wayne Niddery - Winwright, Inc (www.winwright.ca)
SpaceShipOne; GovernmentZero