diff options
author | Matthew Barnes <mbarnes@redhat.com> | 2013-06-17 22:18:02 +0800 |
---|---|---|
committer | Matthew Barnes <mbarnes@redhat.com> | 2013-06-17 22:18:02 +0800 |
commit | 340c64e42d3018942af7bd1ac696d660e57ec082 (patch) | |
tree | 775cd1bcde0eb1d4edd643c91b65a6302a532db1 /e-util | |
parent | 0c2b350db0029ff07fff8b2d5d55a9aedafbfe17 (diff) | |
download | gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.tar gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.tar.gz gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.tar.bz2 gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.tar.lz gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.tar.xz gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.tar.zst gsoc2013-evolution-340c64e42d3018942af7bd1ac696d660e57ec082.zip |
Bug 702454 - EMailBrowser fails to show message
This reworks the MessageList regen scheduling to be a little more
intuitive, at least to me. We now set the RegenData immediately, but
start the actual regen operation from an idle callback. That way the
caller has the remainder of this main loop iteration to make further
MessageList changes without triggering additional regens.
I think what was happening before was we were triggering multiple regen
operations as we were configuring the EMailBrowser, with each new regen
cancelling the previous, and the message UID to select wound up getting
paired with one of the cancelled regen operations. This resulted in no
message UID ever getting selected in the EMailBrowser.
Diffstat (limited to 'e-util')
0 files changed, 0 insertions, 0 deletions