I understand that normally non gui threads can't access gui objects, but in this case it should work, in every other WPF control I use it works fine, presumably because behind the scenes they use Dispatcher.Invoke(...) on all propertychanged notifications.
thanks
7 Answers, 1 is accepted
We have recently added some logic that handles similar cases. What version are you using? If not the latest one, can you please try with the latest version which is 2013 Q1 SP1?
If this does not help, can you send us a very small dummy project that demonstrates the issue you are having and we will debug it immediately to see what exactly is going on.
Thanks in advance.
Rossen Hristov
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.

I'll knock up a little demo when I've got a spare 5 mins, thanks.
We appreciate that. Thanks in advance.
Kind regards,Rossen Hristov
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.

I have replied to the support ticket that you opened.
Greetings,Rossen Hristov
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.

I am copying the other thread here:
Yes, the latest official version is indeed the one that you mentioned (2013 Q1 SP1) and it produces the exception as you said.
But we have managed to resolve this issue. The fix will be released officially with our 2013 Q2 release which is scheduled for June 12th.
Each Monday we release a "Latest Internal Build" version which is for people that want to test before the official version is released. You can find all latest internal builds here.
Here is a direct link to the LIB from April 29th, i.e. this Monday.
Please, let us know if you encounter any other problems.
Rossen Hristov
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.