Click here to Skip to main content
Click here to Skip to main content
Go to top

Tree Structured Enumerations

, 2 Apr 2008
Rate this:
Please Sign up or sign in to vote.
The way to maintain a tree structured enumeration while having all the advantages of the standard ones

Introduction

In this article, I want to show you an approach of how a structured enumeration can be handled by C#.

Background

While playing with my little home project, I stumbled upon a problem of having all those category enumerations displayed in a tree. I wanted to keep it simple - as the enumerations are - while avoiding the need to create structured object hierarchies for every one of them. So, after a bit of thinking, I came up with this solution. I hope you'll find it useful or at least interesting.

Structured Enumeration

First, we have to tickle our old plain list enumeration a bit and convert it to a structured one. I chose the animal categories.. well.. to confess, I'm always having slight difficulties to find a good example, but here it is anyway.

[Structured(100)]
public enum AnimalKind
{
    Unknown         = 00000,

    DomesticAnimals = 00001,
      Dog           = 00100,
        Dalmatin    = 10000,
        Greyhound   = 10001,
        Malamute    = 10002,
        Terrier     = 10003,
      Cat           = 00101,
        
    WildAnimals     = 00002,
      Ape           = 00200,
        Chimpanzee  = 20000,
        Gorrila     = 20001,
        Orangutan   = 20002,
      Deer          = 00201
}

As you might notice, some unknown attribute is used there. Let me introduce it to you.

[AttributeUsage(AttributeTargets.Enum)]
public class StructuredAttribute : Attribute
{
    public int span;

    public int Span
    {
        get { return span; }
        set { span = value; }
    }

    public StructuredAttribute(int span)
    {
        this.span = span;
    }
}

This simple attribute is composed of only one property (an automatic property may be used in C# 3.0, God I love those). The attribute is responsible for determining the span (multiplicator) of the tree levels thus allowing us to distinguish the hierarchy later.

Well.. later is now because this ought to be a short article. I took the liberty to create the utility class to help us deal with the structured enumerations. It consists of two static methods. Let's take a closer look at them.

Methods

The IsChild method is used to determine if one enumeration value is placed under another one. I guess the utility can be easily extended by a method determining the whole chain of the parents from a particular enum value.

public static bool IsChild<ttype>(TType child, TType parent)
{
    Type enumType = typeof(TType);
    Object[] attributeList = enumType.GetCustomAttributes
        (typeof(StructuredAttribute), true);

    if (attributeList.Length > 0)
    {
        StructuredAttribute attribute = (StructuredAttribute)attributeList[0];
        int span = attribute.Span;
        int parentIndex = (int)Convert.ChangeType(parent, typeof(int));
        int childIndex = (int)Convert.ChangeType(child, typeof(int));
        int index = childIndex / span;
        return (index == parentIndex && childIndex != parentIndex);
    }

    return true;
}

Another useful method that may be of interest to us is the CreateList method. It obviously creates a list of the child enumeration values under a particular parental value. It will also allow us to use the output list for the display or various cycle purposes. I can imagine an iterator here.

public static List<ttype> CreateList<ttype>(TType parent)
{
    List<ttype> result = new List<ttype>();
    Type enumType = typeof (TType);
    TType[] enumValues = (TType[]) Enum.GetValues(enumType);
    
    foreach (TType enumValue in enumValues)
    {
        if (IsChild(enumValue, parent))
        {
            result.Add(enumValue);
        }
    }

    return result;
}

Some Examples of Use

This example took all I mentioned above and put it to use. It will dump the tree to a console output while making the levels indented.

private static void DumpTree(AnimalKind parent, Int32 level)
{
    foreach (AnimalKind animalKind in EnumUtility.CreateList(parent))
    {
        string caption = animalKind.ToString();
        int width = caption.Length;
        string output = caption.PadLeft(width + level, ' ');
        Console.WriteLine(output);
        DumpTree(animalKind, level + 1);
    }
}

static void Main()
{
    DumpTree(AnimalKind.Unknown, 0);
    Console.ReadKey();
}

Possible Enhancements

  1. As I said earlier in this article, I can imagine some kind of iterator (or perhaps an indexer) instead of the CreateList method.
  2. The default indexing capabilities of enumerations can be widened by "inheriting" the enumeration from ulong type instead of default uint.
  3. The utility can also be extended with any kind of structuring routine which suits your need such as retrieving the chain of parents for a particular value.

Limitations

  • The complex trees with many levels may find their limit because the indexing will reach the limit of enumeration (ulong). This limitation can be reduced by lowering the span value on the attribute, thus allowing to scale for the count of branches against the count of levels.
  • It is recommended to use some default (zero) value which will then be used to retrieve the level one branches.

Personal Note

I found these structured enumerations quite useful myself dealing with countless - now waiting to be structured - category enumerations. They cut the time needed to create the editable trees where the categories are distinguished from the instance items. Moreover, the enumeration is still one type in the end.

Good luck and I will be pleased to hear your comments.

History

  • 2008-04-02: Missing example was added (Shall I ever get it right the first time?)
  • 2008-04-02: Initial article posted

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Smart K8
Software Developer
Czech Republic Czech Republic
Contacts: EMAIL - smartk8@gmail.com

Comments and Discussions

 
GeneralSuggestions [modified] PinmemberPIEBALDconsult6-Apr-08 17:20 
GeneralSuggestions Part 2 PinmemberPIEBALDconsult6-Apr-08 18:11 
GeneralRe: Suggestions Part 2 PinmemberSmart K86-Apr-08 19:43 
PIEBALDconsult wrote:

In your Attribute, I suggest that the field and/or property should not be publicly modifiable.

 
I missed that. I've got much bigger class EnumUtility I've just stripped away all the code non-concerned in the article. So the compromise:
private int span = 10; // or 0xF maybe
 
public int Span
{
    get { return span; }
}
PIEBALDconsult wrote:
public static bool IsChild<ttype>(TType child, TType parent) // Where if ttype used?
    {
        Type enumType = typeof(TType); // This is needless
        Object[] attributeList = enumType.GetCustomAttributes(typeof(StructuredAttribute), true);
 
        if (attributeList.Length > 0)
        {
            StructuredAttribute attribute = (StructuredAttribute)attributeList[0];
            int span = attribute.Span;  // This is needless
            int parentIndex = (int)Convert.ChangeType(parent, typeof(int));
            int childIndex = (int)Convert.ChangeType(child, typeof(int));
            int index = childIndex / span; // You can simply use attribute.Span here
            return (index == parentIndex && childIndex != parentIndex);
        }
 
        return true;
    }</ttype>

Where if ttype used?: There's no constraint for Enum (it is not possible by C# design) moreover the Attribute is enum only so it ensures that TType will be Enum because otherwise the GetCustomAttributes will be zero.

This is needless: This is my coding pattern of choice (substition pattern) it is IMO more readable then putting altogether (cumulative pattern). Consider this Laugh | :laugh: :
return (((int)Convert.ChangeType(child, typeof(int)) / attribute.Span) ==
       ((int)Convert.ChangeType(parent, typeof(int)) &&
       ((int)Convert.ChangeType(child, typeof(int) != (int)Convert.ChangeType(parent, typeof(int));</br></br>
PIEBALDconsult wrote:
foreach (StructuredAttribute attribute in typeof(TType).GetCustomAttributes(typeof(StructuredAttribute), true))

Fine with me.
PIEBALDconsult wrote:

And, your CreateList calls GetValues on each call; which isn't as costly, but shouldn't be necessary.


I guess there should be some common private class determining the paternity. Such as bool (TType child, TType parent, int span)
 
I'll hear more of your comments and after that I'll modify the article accordingly.
 
regards,
Kate
 
The wisdom is to see things truthfully.



GeneralRe: Suggestions Part 2 PinmemberPIEBALDconsult7-Apr-08 13:42 
GeneralRe: Suggestions Part 2 PinmemberSmart K87-Apr-08 20:43 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web01 | 2.8.140916.1 | Last Updated 2 Apr 2008
Article Copyright 2008 by Smart K8
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid