If you want to use anything more complex than a list of strings in a ListBox, you’re in luck because the control accepts all types of objects.
Custom Objects (Blog Posts) Displayed in a CheckListBox
In this case, I want to display a list of posts found in a blog. Blog is a class which contains Posts, an array of Post classes. To start, I created the CheckedListBox in the form designer, and I add the posts to it like this:
clbPages.Items.AddRange(_blog.Posts);
If I do nothing else, the ListBox will call the Post’s ToString() method and will display as:
Post Post Post Post
We have two options for displaying this correctly:
1. Override the ToString() method. I don’t recommend doing this because ToString() is much more appropriately used in a debugging context.
2. Add a string converter: This will automatically convert each post object to a usable string when called by an object like a ListBox. ListBox uses Convert.ToString() – this uses that converter more appropriately. ToString() should only be used as a fallback.
<pre>
// Use System for the Type object
using System;
// Use ComponentModel for the TypeConvert base class
using System.ComponentModel;
namespace SiteAssistant.Blog
{
/// <summary>
/// Converts a post into a list-friendly string, for checkbox lists
/// </summary>
class PostConverter : TypeConverter
{
/// <summary>
/// Indicates whether the Post can be converted to a destination type
/// </summary>
/// <remarks>
/// We only support conversions to STRING at present
/// </remarks>
/// <param name="context"></param>
/// <param name="destinationType"></param>
/// <returns></returns>
public override bool CanConvertTo(ITypeDescriptorContext context,
Type destinationType)
{
if (destinationType == typeof(string))
return true;
else
return base.CanConvertTo(context, destinationType);
}
/// <summary>
/// Converts the post to the destination type. If the destination
/// type is not supported, the base Conversion is applied.
/// </summary>
/// <remarks>
/// We only support converting posts to strings at present.
/// </remarks>
/// <param name="context"></param>
/// <param name="culture"></param>
/// <param name="value"></param>
/// <param name="destinationType"></param>
/// <returns></returns>
public override object ConvertTo(ITypeDescriptorContext context,
System.Globalization.CultureInfo culture, object value,
Type destinationType)
{
if (destinationType == typeof(string))
{
string text = "";
Post p = value as Post;
// Ensure that the Post is not null, avoid errors
if (null != p)
{
text = p.Title;
}
return text;
}
else
{
return base.ConvertTo(context, culture, value, destinationType);
}
}
}
}
</pre>
The code we write in .NET is like the meat inside a sandwich. The framework is the bread that wraps around our logic and keeps our application together. Our new Posts string converter will be called by the application without us needing to override the Convert function.
It doesn’t happen by magic of course. The final change we have to make is to add information about our conversion function to the posts class:
<pre>
[System.ComponentModel.TypeConverter(typeof(PostConverter))]
public class Post
{
// Rest of the code goes here
}
</pre>
That’s all there is to it! Now we can pass a list of Posts to the CheckedListBox and manipulate each item directly. In this application, I will be using this technique to provide the Post object to the text editor with a double-click.
