views:

1598

answers:

3

Using

<System.ComponentModel.TypeConverter(GetType(System.ComponentModel.ExpandableObjectConverter))> _

on the declaration of a class (which is a property of another class) that consists of a number properties.

I load an instance of this class with simply ...

PropertyGrid1.SelectedObject = oColumn

Obviously I don't want to manually build the propertygrid in code, I know how to do that.

But here's the problem. Depending on the value of a property, certain other properties should not be visible, as though I'd used the

<System.ComponentModel.Browsable(False)> _

attribute on the property declaration.

Is there anyway to do this programmatically, without having to handle all the building of the property grid manually>

+1  A: 

Hi,

if you were hoping for a gridItem.Hide() then, the answer is no. The only way to achieve that in the MS PropertyGrid is to dynamically publish your properties through the GetProperties method of a TypeConverter or custom type descriptor (that implements ICustomTypeDescriptor). I would try first with the TypeConverter (expecially if the property values you want to check are at the same level), there is less coding to do.

Nicolas Cadilhac
+1  A: 

Actually this is entirely possible. The first and easiest way is to set the grid's BrowsableAttributes property:

propGraph.BrowsableAttributes = new AttributeCollection(
    new Attribute[] 
    { 
        new CategoryAttribute("Appearance")
    });

This will filter out all properties that do NOT match the attribute-types you supply. Unfortunately this is a positive filter rather than a negative filter which makes it less useful IMHO.

Second, and equally easy, you can create a simple wrapper around the object you want to display in the PropertyGrid and re-define whatever properties you want to hide/etc. as passthrough properties:

public class MyDerivedControl : public TextBox
{
    [Browsable(false)]
    [Category("MyCustomCategory")]
    public new bool Enabled
    {
         get { return base.Enabled }
         set { base.Enabled = value; }
    }
}

Pop that into a property grid and the Enabled property will be hidden.

Third, you can customize the PropertyGrid itself and get into the world of type descriptors and so forth, but if all you want to do is hide a couple properties, this is overkill.

Hope this helps.

James D
A: 

This Question is similar, but the answers are more complete. Some people may wish to cross reference.

rathkopf