SL wcf proxies are asyc only due to not wanting to lock the UI which means that my first guess would be that the animation is using a background thread as well (under the hood) which is the same thread as the wcf (under the hood) thread for detecting a response.
It doesn't make sense that the wcf call would block the UI as that's the whole reason for having async calls. Is the animation stopping or just stuttering? It may be a thread polling for a response from the service which is blocking the animation. On Thu, Feb 19, 2009 at 9:24 AM, Stephen Price <[email protected]> wrote: > Hey all > I've notices some of my animations are not running smoothly and it > seems to happen when I make wcf service calls. The call is asyc > judging by it's name and callback but it would appear to be blocking > the ui thread. > From memory I've hit this before in the past when I was working with > SPF and I think I used a background worker to kick the work off on > it's own thread but that doesn't seem right for an asyc wcf service > call? > Anyone come across this before? If I comment out the service call the > animation works fine. (it's a busy/loading/waiting type animation that > I want to run until the callback is called when the results come back. > Ta > Stephen > -------------------------------------------------------------------------------- > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > > -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozsilverlight Other lists you might want to join: http://www.codify.com/lists
