Bug 699223 - Emit view signals from context where view was started
authorMatthew Barnes <mbarnes@redhat.com>
Fri, 3 May 2013 17:14:53 +0000 (13:14 -0400)
committerMatthew Barnes <mbarnes@redhat.com>
Fri, 3 May 2013 17:28:59 +0000 (13:28 -0400)
commit417164c733128072ea3e4ad685829f0c3270c1b7
treed3281fb2efefe653b77d3ec38c39ce7c714412f1
parentc6a76b8d21ffb88260e8d42bde19a8af1ea3882f
Bug 699223 - Emit view signals from context where view was started

This applies to both EBookClientView and ECalClientView.

Incoming D-Bus signals were being propagated to the EClient's main loop
context, but there may not be a running main loop on that thread, so the
main loop sources were never being dispatched and the view signals never
emitted.

Instead use the main loop context which was the thread-default at the
time the view was started, which is often the so-called "main" thread
where a main loop is more likely to be running.
addressbook/libebook/e-book-client-view.c
calendar/libecal/e-cal-client-view.c