aboutsummaryrefslogtreecommitdiffstats
path: root/m4
diff options
context:
space:
mode:
authorMatthew Barnes <mbarnes@redhat.com>2013-02-25 21:53:34 +0800
committerMatthew Barnes <mbarnes@redhat.com>2013-02-25 22:27:35 +0800
commit5fdcdbc7854c2e3f075619e8b34734c922167b59 (patch)
treeda5dcfe82fd75d496b4bb9bfefbeadfa4df6a0df /m4
parentf5d1b8bc5a40700e81dc1162ba0206cd55daaa9e (diff)
downloadgsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.tar
gsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.tar.gz
gsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.tar.bz2
gsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.tar.lz
gsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.tar.xz
gsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.tar.zst
gsoc2013-evolution-5fdcdbc7854c2e3f075619e8b34734c922167b59.zip
EAddressbookModel: Listen to the cache for client readonly changes.
Change notifications for EClient's "readonly" property can come on any thread. Our "notify::readonly" signal handler immediately updates the model's editable status, which triggers GTK+ calls, which can crash the application if we're not in the correct thread. Connect instead to EClientCache's "client-notify" signal, which is always emitted from EClientCache's dedicated main loop context, and happens to be the same main loop context that GTK+ uses. It's also less bookkeeping when the model's EBookClient gets replaced.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions