Advanced Forum Search Results
-
Hey,
Are you sure it worked in Beta? In you sample I don't see how do you set DataContext of the UserControl. This XAML:
<Controls:TabItem DataContext="{Binding Path=dataItem[0]}">
means: "Bind TabItem's DataContext to the first element of list returned by dataItem property from parent's DataContext". It ...
-
Hey,
Unfortunately, this is a bug in Silverlight. The workaround is to redefine the custom XML prefix on root element from the ControlTemplate (but this time you have to include assembly name as well), like in the sample below: 1 <UserControl x:Class="BindingAttachedDPsInTemplate.MainPage"
2 ...
-
Hey,
It should work fine in Beta 1. What kind of control did you use? Can you share a small repro?
Best regards,
Tomek
-
Hey,
But the binding doesn't have concept of "dirty objects" - it uses concept of "dirty properties", and that's why it doesn't listen for all PropertyChanged notifications, but only for notifications that affect properties on the path.
[quote user="tony_lombardo"]
[quote user="Tomek ...
-
Hey,
The binding engine updates the target only when properties on the path change. When you use an empty path, the engine has nothing to listen for and it works as one-time binding.
I wouldn't call it a bug, but rather design limitation. Even if the engine listened for all changes on all objects on the property path (what would decrease ...
-
Hey,
Can you share MyControl implementation and template?
Best regards,
Tomek
-
Hey,
I guess you want to use pElement inside the handler. If it is the case, you can use lambda expressions.
1 vStoryboard.Completed += (sender, e) =>
2 {
3 if (pElement == "First)
4 ...
5 }
As you ...
-
Hey,
No, multibinding won't be supported in Silverlight 3.
Best regards,
Tomek
-
Hey,
In Silverlight 2 you can set Style property only once and if you try to set it again, you will get an exception. This limitation was removed in Silverlight 3 Beta.
Best regards,
Tomek
-
Hey,
Unfortunately, there is no easy way to achieve two way binding in your case with Silverlight 2.0. You are right - you only get the change value in ConvertBack method. If the array has always one item and if it can be replaced, you can return a new array from ConvertBack; otherwise, it may be easier not to use binding in this ...