For accounts linked to an Online Accounts service (GNOME or Ubuntu),
display an informational message with an "Open Online Accounts" button
that launches gnome-control-center with an appropriate panel name.
This removes all traces of Express Mode from all but the contact editor
and calendar appointment editor. Need to evaluate the remaining cases
individually.
EShellSettings predates GSettings and is no longer necessary.
GSettings allows binding GObject properties to GSettings keys,
with optional mapping functions. That fulfills the purpose of
EShellSettings.
Replaces "paned-view-headers-state", which was defined as an integer for
some stupid reason. Not bothering to migrate the old setting since it's
one button click.
In some cases the collection source is non-writable but its child
sources _are_ writable. In that case, the one non-writable source
causes the whole operation to fail. Commit only writable sources.
Evolution could crash when changing message view, like when
toggling Show Deleted messages. This effectively reverts
the previous commit and propagates the same changes further
in the code.
Remove EMailTagEditor's "use-24-hour-format" and "week-start-day"
properties, which were being used to manually configure its internal
EDateEdit instance. This is unnecessary since all EDateEdit instances
are automatically configured by the ESettingsDateEdit extension.
ESourceCollection's default backend name is "none". Unfortunately so
is CamelNullStore's provider name. Make sure these two misfits don't
get paired up!
Replaces em_utils_in_addressbook().
Foregos any address caching since any such cache would likely not be
updated properly as contacts are added and removed and would lead to
incorrect results.
An asynchronous variation of this function can be easily added at some
future date should a need arise.
GTK+ uses (G_PRIORITY_HIGH_IDLE + 20) for redrawing operations, which is
actually a slightly lower priority than G_PRIORITY_HIGH_IDLE. Therefore
for our purpose, G_PRIORITY_HIGH_IDLE is sufficient.
This reverts commit 2b507716b2.
The commit contains not a single comment as to why these custom priority
values are being used. The rationale needs to be documented in the code,
either at each call point or preferrably at a centralized priority value
definition.
Might be the final change for this bug, the two previous commits
were not using the right approach, causing regression in rendering
of text/* parts which were not named in the list of excluded content
types for a 'raw' formatting.
