tag:blogger.com,1999:blog-3198935374994345981.post5790216224279594840..comments2009-02-03T16:48:14.211+01:00Comments on Coding Instinct: WPF Action Dispatch with CaliburnTorkel Ödegaardnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3198935374994345981.post-57018783432337620412009-02-03T16:48:00.000+01:002009-02-03T16:48:00.000+01:00Yea I saw the base class in Caliburn, but most of ...Yea I saw the base class in Caliburn, but most of the background logic was handled in threads other than the UI. A batching feature would be great, I have noticed that the WPF dispatcher can easily get flodded.Torkel Ödegaardhttp://www.blogger.com/profile/08914354140151859277noreply@blogger.comtag:blogger.com,1999:blog-3198935374994345981.post-33519598368524523712009-02-03T14:57:00.000+01:002009-02-03T14:57:00.000+01:00Great to see you are trying out Caliburn! Please ...Great to see you are trying out Caliburn! Please feel free to send me feedback at any time. I though I would mention that Caliburn has a PropertyChangedBase which implement INotifyPropertyChanged for you. Presently, it doesn't marshall events to the UI thread as you do in your example, but in the next week I am planning on fixing that. Along with this will come some support for performant batching of large amounts of events to the UI, for scenarios where there are intesive model changes.Robhttp://www.blogger.com/profile/02668400456946681406noreply@blogger.com