Yes, there have been some improvements in this scenario. There are is now the “Binding Groups” feature which allows the user to more easily submit a group of explicit bindings. You can read more about this feature in Vincent’s blog.

Bea

Bea

RelativeSource bindings will be re-evaluated every time there is a change in layout. More specifically, RelativeSource bindings are evaluated 1) when SetBinding is called, 2) by a method that is queued in the dispatcher at a priority lower than layout, and 3) every time we get a layout changed event. The relative binding source may not exist while layout is still happening, but once layout settles, the source will be there. We will retry evaluating the binding until that happens. You can find the code for this in the AttachToContext method of BindingExpression.

Let me know if this helps.

Bea

At first sight, both the first and second methods seem to be equally good. The first method has the slight advantage that you don’t need to know the name of the DataTemplate. The third method won’t work anytime you’re looking for an element within the DataTemplate, like in this sample. If you’re looking for something within the ControlTemplate, the third method is the best, quickest way to get a handle to the element.

Thanks,
Bea

Bea

It should be possible to do what you’re asking by using BeginInvoke. There are a few things that you will want to keep in mind:

1. Don’t do a BeginInvoke with a priority higher than what is necessary. This may cause your app to slow down.
2. Don’t forget to lock your data.
3. Don’t call BeginInvoke before the previous BeginInvoke call has been process from the queue – this can also cause delays. You can write some code like the following:

// this code should be called by the worker thread
lock(this)
{
…store data items for later use by the UI thread
if(this.dispatcherOperation == null)
{
this.dispatcherOperation = Application.Current.Dispatcher.BeginInvoke(DispatcherPriority.Normal, …this.MyFunction…);
}
}

// this will be called in the UI thread
private void MyFunction(…)
{
lock(this)
{
…add items to the ListView
this.dispatcherOperation = null;
}
}

Thanks,
Bea

If I understand correctly, you are asking for a way to call UpdateSource on all bindings below a certain element in the tree. We’ve talked about that on the data binding team, but never got around to doing it. Our idea was to add a Bindings collection to certain elements, which would contain all the Bindings associated with child elements in the same namescope. To update all bindings of a particular user control, you would simply have to get the Bindings collection for that control, enumerate through all BindingExpressions and call UpdateSource() on them.

Unfortunately I very much doubt that this feature will be included in our next release, given our current planning – unless of course, there is a lot of customer demand. So scream if you would like to see us implement that :)

Until then, we need to continue doing that manually… :(

Thanks a lot for your feedback!!

Bea

Yes, it does make sense. Unfortunately that is the current behavior of ObjectDataProvider and I can’t think of a simple workaround to call the method for each item. A similar question has been answered in the WPF forum recently.

Thanks,
Bea

Please see my reply to Tony B, below. I modified this sample to behave the way you guys want – you can find my code here.

Thanks,
Bea