The event aggregator itself in our implementation is aware of a synchronization context for WPF being the Dispatcher. There is a good read here<http://codebetter.com/blogs/jeremy.miller/archive/2009/07/23/how-i-m-using-the-event-aggregator-pattern-in-storyteller.aspx>, and is what we used as a starting point for our usage. I don't think the form itself should be responsible for any updates, but rather something like a presenter. At that point you make a choice to immediately update the UI, or defer to only update periodically if that makes sense.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
