Nick, Pertti --

>>So, the short answer is: visual inheritance in .Net *kind of* works, but pretty much useless. :)
>
>well, yeah... seems like a lot of typing & reliance on "tribal knowledge" instead of just changing the damn font properties in the parent class and being done with it.

"Tribal Knowledge"? Jeez, that's a bit over the top.

There's a perfectly acceptable and correct way of doing this and, as Kevin mentioned, if it's done right when you are first designing your controls, it is not an issue. The visual inheritance works just fine.

So, you have to know the right way to design your controls before you begin designing your controls ... I don't think that constitutes "tribal knowledge" any more than knowing the right way to do things in VFP does. A little research goes a long way. <g>

~~Bonnie




>
>
>>
>>>... unbelievable ... save your hair: how about doing this project with VFP ... <g>
>>>
>>>>I am beginning to pull my hair out over this. Nothing I do causes a change in the appearance of the font on the screen. Help- pleassssse.....
>>>>
>>>> [DefaultValue(typeof(Font), "Arial,8pt")]
>>>> public override Font Font
>>>> {
>>>> get { return base.Font; }
>>>> set { base.Font = value; }
>>>> }
>>>>
>>>> public wrLabel()
>>>> {
>>>> InitializeComponent();
>>>> this.Font = new Font("Arial", 8);
>>>> // tried base.font=new Font('Arial',8); but it doesn't change the font on the screen either
>>>> }