Theory question

  • Thread starter Thread starter YYZ
  • Start date Start date
Y

YYZ

Can anyone tell me why (not accusing .Net, just wondering) if I make a property
on a form Public, then inherit from that form, then I can see the property in
the form's property window (good), but if I make the property protected, I can't
(bad)?

I'm trying to see the logic in that...and I haven't found it yet.

Matt
 
YYZ said:
Can anyone tell me why (not accusing .Net, just wondering) if I make
a property on a form Public, then inherit from that form, then I can
see the property in the form's property window (good), but if I make
the property protected, I can't (bad)?

I'm trying to see the logic in that...and I haven't found it yet.
Click to expand...

I think the logic is that protected means that only derived classes can
access it. As the designer is not a derived class, it is not possible for
the designer to set/get it.


--
Armin

How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html
 
Armin Zingler said:
I think the logic is that protected means that only derived classes can
access it. As the designer is not a derived class, it is not possible for
the designer to set/get it.
Click to expand...

Thanks. I can see what you are saying. I don't like it <g>, but I understand
now.

Matt
 
Back
Top