>My point was that the 'template' provides me with the visual cues of the default _potential_ behavior that may or may not need to be modified. And I don't have to remember all the stinking numbers and/or names.

I understand. However, whats more visual, I giant case statement with numbers, or a list of methods and events that can be viewed from a class browser like utility or intellisense?

What happens if the template needs changing? How many case statements will need updating?

>Call me lazy.

A Lazy Developer. Somehow, I don't think you're the first :-P

When you think about it, doing the dirty work early on, lets you be lazier when the time comes to both use and update your class :-)