Now I have an answer to my question. This is not the answer I was originally looking for, and it is a bit long, but it works.
I read this post by Josh Smith. He recommends not using value converters, but pushing calculations into the view model and exposing them as a property:
http://groups.google.com/group/wpf-disciples/browse_thread/thread/3fe270cd107f184f?pli=1
In my case, the text for "textBox1" and "textBox2" should be attached to the view model, so when they change in the view model, I know that it takes time to calculate and update the dependent property. The dependent property then fires its modified property event and updates from it.
If you have a case where you want an expression to depend on read-only control properties that you cannot easily bind to a view model, you can follow these tips:
Pushing read-only GUI properties back to ViewModel
I would still like to be able to embed (not business logic) expressions in XAML. But, seeing that this is not a built-in way to do this is likely to be a little hack. Going through the presentation model seems to be the right way to do this, but maybe one day I will be experimenting with writing a markup extension that allows expressions in XAML.
Ashley davis
source share