>>...I was curious because I have never seen a sample with it being subclassed, so I was beginning to think there might be some downside I didn't know about.
>
>That's because examples are almost always over-simplistic, rarely reflecting real-world stuff. Unfortunately. =0(
>
>I say sub-class everything!!! (How's that for over-simplistic! <g>)
>
>~~Bonnie

Agree, makes adding global features later a breeze. Subclassing so far in WPF has been a tad harder than in WinForms. Mostly because it took me a while to understand the templating. Now that I'm getting templating down, it's getting a lot easier.

One of these days I need to debug why all my custom controls are all greyed out in the toolbar. :(

(Edit... crashed VS a few times, but I got them working.)