Strange. The Property *should* show up in your Property Sheet. I have plenty of controls sub-classed from UserControl, so I know it works. The only thing I can think of is that it might have something to do with the type of property being something called TWWebBrowser (I don't know what that is). Maybe a reference needs to be added? I don't know ... just guessing.
~~Bonnie
>Perhaps, I misunderstood your point. Assuming I've got user control with a split container and 2 browser controls in the panels.
>I created a property , though member fullViewBrowser is internal anyway.
>
> public partial class HtmlHitlist : UserControl
> {
>
> public TWWebBrowser FullViewBrowser
> {
> get { return fullViewBrowser; }
> set { fullViewBrowser = value; }
> }
>>I put control on a form tab page as htmlHitList1
>Am I supposed to see FullViewBrowser in Properties for that form ? Probably not, as I don't. For some reason in VS they decided to treat usercontrol as a black box in designer view. Surely either member or property are accessible in a code.
>
>
> protected override void OnShown(EventArgs e)
> {
>
> base.OnShown(e);
> this.htmlHitlist1.FullViewBrowser.DocumentText = "<html><hr><h2>Full view</h2><hr></html>";
> this.htmlHitlist1.fullViewBrowser.DocumentText = "<html><hr><h2>Full view</h2><hr></html>";
>
> ...
>>
>
>>>Just curious , does similar limitation apply to usercontrol used as a container. Unlike Visual Foxpro when placed on a form, children are not editable via property sheet regardless of access modifier. No problem to deal with them programmatically.
>>
>>No, there is no such limitation with UserControls ... but to be able to edit them via the Property Sheet, you would need real properties (with get/set), rather than simply protected or public modifiers.
>>
>>~~Bonnie
>>
