At the moment I'm using most of my time for learning WPF, because a while ago I got the crazy idea (I must have been drunk) that this could become my first MCTS certificate ;-). Since then I'm experiencing a continuos up and down everytime I open my Visual Studio. I mean - hey - wouldn't it be boring to always know what a method returns? I haven't casted as much as since I know WPF - and it's always a pleasure to think about what I could insert into a method, which expects only a completly unknown interface.

The first book I used for studying was, of course, the Microsoft "Training Kit". And exactly in that book I found a funny example that can demonstrate my feelings as good as nothing else.

The example explains how to write my own custom-button - I didn't keep the colors of the example I must confess - but all summed up I got something like this:

While I was enjoying the beautiful animation I was able to attach to the button (it got shrunk almost invisible and returned to its origin size), I recognized that there was something strange: The button got smaller and smaller ...

Obviously WPF replaces the origin size of the button, when it's clicked before the AutoReverse of the Animation finished. Ok - in some way this might be logical, because otherwise you wouldn't be able to handle an object that just is being animated. But I think this is one of the many small things that give WPF some kind of unfinished touch...