so if I have this correct: 1. you have forms 2. forms subscribe to an event aggregator 3. the event aggregator is located on the main thread 4. the consumers push updates to the event aggregator, somehow marshaling thread contexts 5. the aggregator then publishes updates to the forms which are on the same thread
so in this scenario the forms/presenters are not driving GUI updates. the aggregator is. the forms are passively awaiting updates. correct? if my 5 step process above is accurate. how, specifically, are you managing thread contexts and pushing updates from the consumer to the aggregator? On Oct 7, 12:51 pm, Corey Kaylor <[email protected]> wrote: > In one of our WPF application we have used RSB to send and receive messages. > The way we update the UI thread is by using an event aggregator from the > clients consumer. In our case all event aggregator messages are sent on the > UI thread. The only thing I'm not particularly fond of is that very few > messages that we've used are sent via Notify and the automatic subscriptions > that occurs in RSB is unnecessary because Send / Reply will work fine > without any awareness of subscriptions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
