Is it possible to tell the WPF binding to respond asynchronously to a PropertyChanged event (low priority)?

IsAsync is good, but you should determine correctly which one of your property change (caused by assignement of new data) require long running task, then put it there. CMIIW IsAsync on your data trigger binding didn't work because to to perform changes on IsFiltered is only a simple task don't require long running task.

IsAsync is good, but you should determine correctly which one of your property change (caused by assignement of new data) require long running task, then put it there. CMIIW IsAsync on your data trigger binding didn't work because to to perform changes on IsFiltered is only a simple task don't require long running task. So find out which one of the property change possibly took long running task put the IsAsync = True there.

Hope that help.

It doesn't really help. As you rightly point out getting a bool is not really a slow operation. The problem is that I've created a situation where a large number of PropertyChanged events are being fired at the end of a bulk operation.

I'll probably have to split the bulk operation up, which will also slice up the IsFiltered updates and allow the rest of the UI a chance to update also. I don't think I want to try leveraging IsAsync, since it wasn't really intended for this kind of usage. – Christo Aug 30 '10 at 11:12.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.