Hiding inherited members

[Troy Hilbert]

I've created a class derived from NativeWindow. The public methods are
visible to consumers of my class and I don't wish them to be. How does one
hide those members?

Best

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003

[Mike M]

I was actually going to ask the same question. I'll give
you an example though.

If you look at the TrackBar control, there is no Text
property because there is no text rendered on the
control. The TrackBar inherits from the Control class,
which does have a Text property.

From what I understand, using the keyword new is supposed
to allow you to replace an inherited function with your
own. This doesn't work if you change the scope.

If I remember correctly, changing the scope does work in
VB with the Shadows keyword. I would assume that C#
would have some way to do it.

-----Original Message-----
I've created a class derived from NativeWindow. The public methods arevisible to consumers of my class and I don't wish them to be. How does onehide those members?

Best

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003

.

[Jon Skeet]

Mike M <mi*********@bcbskc.com> wrote:

I was actually going to ask the same question. I'll give
you an example though.

If you look at the TrackBar control, there is no Text
property because there is no text rendered on the
control.

But TrackBar *does* have a Text property. I'm not sure why it's not
document, but it *does* exist:

using System;
using System.Windows.Forms;

public class Test
{
static void Main()
{
TrackBar tb = new TrackBar();
tb.Text="hello";
}
}

compiles fine.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

[Mike M]

Then it must be hidden. It doesn't show up in the
intelliSense, which is good enough to avoid confusion.
The BrowsableAttribute just makes it so that it doesn't
show up in the property browser. I was wondering if the
ObsoleteAttribute might do it, but I it doesn't look like
it.

-----Original Message-----
Mike M <mi*********@bcbskc.com> wrote:

I was actually going to ask the same question. I'll give you an example though.

If you look at the TrackBar control, there is no Text
property because there is no text rendered on the
control.
But TrackBar *does* have a Text property. I'm not sure

why it's notdocument, but it *does* exist:

using System;
using System.Windows.Forms;

public class Test
{
static void Main()
{
TrackBar tb = new TrackBar();
tb.Text="hello";
}
}

compiles fine.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too
.

[Jon Skeet]

Mike M <mi*********@bcbskc.com> wrote:

Then it must be hidden. It doesn't show up in the
intelliSense, which is good enough to avoid confusion.
The BrowsableAttribute just makes it so that it doesn't
show up in the property browser. I was wondering if the
ObsoleteAttribute might do it, but I it doesn't look like
it.

I believe you're looking for EditorBrowsableAttribute.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

[Mike M]

Awesome. Thanks. You wouldn't happen to know where I
can find a nice, neat list of ALL the attributes, would
you? I found one in help, but either I'm blind or it
wasn't in the list.

-----Original Message-----
Mike M <mi*********@bcbskc.com> wrote:

Then it must be hidden. It doesn't show up in the
intelliSense, which is good enough to avoid confusion. The BrowsableAttribute just makes it so that it doesn't show up in the property browser. I was wondering if the ObsoleteAttribute might do it, but I it doesn't look like it.

I believe you're looking for EditorBrowsableAttribute.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too
.

[Jon Skeet]

Mike M <mi*********@bcbskc.com> wrote:

Awesome. Thanks. You wouldn't happen to know where I
can find a nice, neat list of ALL the attributes, would
you? I found one in help, but either I'm blind or it
wasn't in the list.

If you look up System.Attribute in MSDN and then expand "Derived
Classes" you'll get the immediately derived ones. It's in that list -
but it's a pretty big list!

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

[Mike M]

Thanks

-----Original Message-----
Mike M <mi*********@bcbskc.com> wrote:

Awesome. Thanks. You wouldn't happen to know where I
can find a nice, neat list of ALL the attributes, would you? I found one in help, but either I'm blind or it
wasn't in the list.
If you look up System.Attribute in MSDN and then

expand "DerivedClasses" you'll get the immediately derived ones. It's in that list -but it's a pretty big list!

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too
.

[Troy Hilbert]

Thanks, I was leaning in that direction after spelunking around MSDN. Man
I've got much to learn about object oriented design principles. Have any
recomendations for neophytes?
"Jon Skeet" <sk***@pobox.com> wrote in message
news:MP************************@news.microsoft.com ...

Troy Hilbert <th******@spamfree.hotmail.com> wrote:

I've created a class derived from NativeWindow. The public methods are
visible to consumers of my class and I don't wish them to be. How does one hide those members?

You don't. That would violate Liskov's Substitutability Principle, for
a start. I suggest you have a NativeWindow as a field within your class
rather than deriving from it.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003

[Jon Skeet]

Troy Hilbert <th******@spamfree.hotmail.com> wrote:

Thanks, I was leaning in that direction after spelunking around MSDN. Man
I've got much to learn about object oriented design principles. Have any
recomendations for neophytes?

Write lots of code, work out what's unpleasant about it, and learn from
that. I dare say there are plenty of books that would help out (the
Gang of Four "Design Patterns" book, for instance) but experience is
the best teacher. There's nothing like doing it wrong to teach you to
do it right :)

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too