This question is locked. New answers and comments are not allowed.
I'm working with the RadDataBoundListBox in a big project with lots (50-100) of images in a list. I know that there is normally a problem with the image control where it loads the image on the UI thread, blocking it. (see here http://blogs.msdn.com/b/delay/archive/2010/09/02/keep-a-low-profile-lowprofileimageloader-helps-the-windows-phone-7-ui-thread-stay-responsive-by-loading-images-in-the-background.aspx)
Because of this problem, before we got the RadDataBoundListBox, we were using the low profile image loader (LPIL). Since moving to the Telerik controls, we've been less distracted by horrible performance (you guys rock!) and started noticing that when I use the low profile image loader (LPIL) code with the RadDataBoundListBox, I will frequently get the wrong image assigned to a given item. (I think this is a problem with the LPIL code, not the RadDataBoundListBox). Because of this, I switched our data template from
<Image lowProfile:LowProfileImageLoade.UriSource={Binding MyImage} />
to
<Image Source={Binding MyImage} />
However, one of our back-end devs now says that the image loading is blocking the UI thread. I'm not a threading guru (I'm a designer to wanders disasterously into code every now and then) so I wanted to ping someone at Telerik about this... I kind of got the feeling that your control did some kind of magic to solve that problem. Am I wrong? Do I still need to find an image loading threading solution?
Because of this problem, before we got the RadDataBoundListBox, we were using the low profile image loader (LPIL). Since moving to the Telerik controls, we've been less distracted by horrible performance (you guys rock!) and started noticing that when I use the low profile image loader (LPIL) code with the RadDataBoundListBox, I will frequently get the wrong image assigned to a given item. (I think this is a problem with the LPIL code, not the RadDataBoundListBox). Because of this, I switched our data template from
<Image lowProfile:LowProfileImageLoade.UriSource={Binding MyImage} />
to
<Image Source={Binding MyImage} />
However, one of our back-end devs now says that the image loading is blocking the UI thread. I'm not a threading guru (I'm a designer to wanders disasterously into code every now and then) so I wanted to ping someone at Telerik about this... I kind of got the feeling that your control did some kind of magic to solve that problem. Am I wrong? Do I still need to find an image loading threading solution?