This question is locked. New answers and comments are not allowed.
Why does
work but
not? I see the example in the demo which switches to German and it manages the resources itself. This seems completely unintuitive to me. What have I missed??
Tim
| <TextBlock Text="{Binding Path=Resource.Path, Source={StaticResource i18n}}"/> |
work but
| <T:GridViewDataColumn HeaderText="{Binding Path=Resource.Path, Source={StaticResource i18n}}" UniqueName="..."/> |
not? I see the example in the demo which switches to German and it manages the resources itself. This seems completely unintuitive to me. What have I missed??
Tim
3 Answers, 1 is accepted
0
Hello Tim,
Unfortunately this is a limitation of the Silverlight platform. It does not allow you to databind properties of objects which did not derive from FrameworkElement. Our columns are DependencyObjects, which did not provide databinding capabilities in Silverlight. This works fine on WPF.
Kind regards,
Stefan Dobrev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Unfortunately this is a limitation of the Silverlight platform. It does not allow you to databind properties of objects which did not derive from FrameworkElement. Our columns are DependencyObjects, which did not provide databinding capabilities in Silverlight. This works fine on WPF.
Kind regards,
Stefan Dobrev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Tim
Top achievements
Rank 1
Rank 1
answered on 23 Jul 2009, 12:58 PM
Thanks. Unfortunately, most of the Silverlight documentation points to WPF which is of course a source of confusion here. Do you have any plans to change this?
Tim
Tim
0
Hi Tim,
We share some part of the documentation between the two platforms, because as you may know our code-base and API are the same. Can you point me to any the specific "broken links" (Silverlight link pointing to WPF) so that we can fix them?
Kind regards,
Stefan Dobrev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
We share some part of the documentation between the two platforms, because as you may know our code-base and API are the same. Can you point me to any the specific "broken links" (Silverlight link pointing to WPF) so that we can fix them?
Kind regards,
Stefan Dobrev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.