aboutsummaryrefslogtreecommitdiffstats
path: root/e-util/e-activity-bar.c
Commit message (Collapse)AuthorAgeFilesLines
* Properly disconnect signal handlers added with e_signal_connect_notify*()Milan Crha2014-06-051-1/+1
| | | | | | | | | | | This is a follow-up for the previous commit, where e_signal_connect_notify*() functions had been added. Due to a different callback and user data being attached to the 'notify' signal, the g_signal_handlers_*() functions do not work properly, thus these e_signal_connect_notify*() functions need a different way for a signal handler disconnect. A side-change was done in e-settings-web-view-gtkhtml.c, checking for a real key change from GSettings.
* Ignore false GObject property change notificationsMilan Crha2014-06-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | This is related to bug 698275, which did not cover all cases. The problem here is that the dconf can in certain situation claim that everything changed (path "/" changed), which GSettingsBinding propagates to a GObject property unconditionally and GObject's property setter (g_object_set_property()) also notifies about the property change unconditionally, despite the real descendant property setter properly checks for the value change. After all these false notifications a callback on "notify" signal is called and possibly an expensive operation is run. Checking whether the value really changed helps in performance, for which were added new e-util functions: e_signal_connect_notify() e_signal_connect_notify_after() e_signal_connect_notify_swapped() e_signal_connect_notify_object() which have the same prototype as their GLib counterparts, but they allow only "notify::..." signals and they test whether the value really changed before they call the registered callback.
* [EActivityBar] Reset priv->timeout_id when the timeout is reachedMilan Crha2014-04-241-2/+39
| | | | | | | Since GLib begun to claim about incorrect ids being passed to g_source_remove(), a problem with EActivityBar had been discovered, it doesn't unset its priv->timeout_id when the timeout is reached, which leads to the new runtime warnings from GLib.
* Stop using deprecated gtk-stock itemsMilan Crha2014-02-131-3/+6
|
* Bug 721545 - License text contains obsolete FSF postal addressMatthew Barnes2014-01-081-10/+9
|
* Bug 710797 - Name all the timeouts added with g_timeout_add()Bastien Nocera2013-10-301-4/+4
|
* Add e_activity_cancel().Matthew Barnes2013-04-251-3/+1
| | | | Convenience function cancels the activity's GCancellable.
* Bump GDK_VERSION_MIN_REQUIRED to GDK_VERSION_3_2.Matthew Barnes2013-01-201-1/+1
| | | | | Clean up resulting deprecation warnings, which were all related to GtkOrientable consolidation (e.g. gtk_hbox_new() -> gtk_box_new()).
* Consolidate base utility libraries into libeutil.Matthew Barnes2012-12-131-0/+366
Evolution consists of entirely too many small utility libraries, which increases linking and loading time, places a burden on higher layers of the application (e.g. modules) which has to remember to link to all the small in-tree utility libraries, and makes it difficult to generate API documentation for these utility libraries in one Gtk-Doc module. Merge the following utility libraries under the umbrella of libeutil, and enforce a single-include policy on libeutil so we can reorganize the files as desired without disrupting its pseudo-public API. libemail-utils/libemail-utils.la libevolution-utils/libevolution-utils.la filter/libfilter.la widgets/e-timezone-dialog/libetimezonedialog.la widgets/menus/libmenus.la widgets/misc/libemiscwidgets.la widgets/table/libetable.la widgets/text/libetext.la This also merges libedataserverui from the Evolution-Data-Server module, since Evolution is its only consumer nowadays, and I'd like to make some improvements to those APIs without concern for backward-compatibility. And finally, start a Gtk-Doc module for libeutil. It's going to be a project just getting all the symbols _listed_ much less _documented_. But the skeletal structure is in place and I'm off to a good start.