summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2015-10-05Bump version to 1.10.2mate-notification-daemon-1.10.21.10monsta2-1/+7
2015-08-08Use accessor functions instead of direct accessinfirit2-7/+10
2015-08-08Help: remove useless help button from guiraveit652-39/+2
+ little GUI adjustments, looks better with two buttons
2015-07-31standard: Fix crash due to incorrectly destroying widgetinfirit1-1/+1
Fixes #69
2015-07-24Fix comparison between unsigned and signed intinfirit1-1/+1
2015-07-24Fix several incompatible pointer type warningsinfirit4-4/+4
2015-07-24Fix warning _FORTIFY_SOURCE is redefinedinfirit1-1/+1
2015-07-23Do not use g_assert_nonnullinfirit1-2/+2
This was added in Glib 2.40 and we still target 2.36.
2015-07-22Bump version to 1.10.1mate-notification-daemon-1.10.1Monsta2-1/+6
2015-07-22all themes: don't crash on notifications from RhythmboxMonsta4-4/+4
fixes https://github.com/mate-desktop/mate-notification-daemon/issues/55
2015-07-19daemon: exit with 0 on idleGiedrius Statkevičius1-3/+1
Exit with 0 (EXIT_SUCCESS) on idle due to the fact that some D-Bus implementations like kdbus are tracking daemons' exit codes and will mark mate-notification-daemon as if it failed if it exits with 1.
2015-07-09daemon: clean up {add,remove}_exit_timeout()Giedrius Statkevičius1-4/+4
Add a nonnull assertion, remove unnecessary {} around one return statement
2015-07-09daemon: use gbooleans instead of guint bit fieldsGiedrius Statkevičius1-2/+2
Almost everything about bit fields are implementation defined and there is a special type for storing booleans (which these bit fields were used for) so use that instead because of portability
2015-06-17GTK3: Fix positioning notifications with long textraveit656-0/+53
Closes https://github.com/mate-desktop/mate-notification-daemon/pull/52
2015-06-12Sync translations with transifexmate-i18n10-66/+73
2015-05-04Bump version to 1.10.0mate-notification-daemon-1.10.0Stefano Karapetsas2-2/+2
2015-03-02Bump version to 1.9.90mate-notification-daemon-1.9.90Stefano Karapetsas2-3/+3
2015-03-02first connect to settings, then read them.Monsta3-8/+10
fixes the issue with GLib >= 2.43, https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 Closes https://github.com/mate-desktop/mate-notification-daemon/pull/45
2015-03-02Sync translations with transifexmate-i18n9-39/+45
2015-01-20Sync translations with transifexmate-i18n56-472/+486
2014-12-31Sync translations with transifexmate-i18n4-12/+371
2014-12-31capplet: use "popup" instead of "pop-up" everywhere for consistencyMonsta1-2/+2
fixes https://github.com/mate-desktop/mate-notification-daemon/issues/35
2014-12-31daemon: fixed logic in a couple of placesMonsta1-2/+2
2014-12-23don't leak memoryMonsta1-5/+7
2014-11-10Bump to 1.9.1mate-notification-daemon-1.9.1Stefano Karapetsas2-2/+2
2014-10-23Sync translations with transifexmate-i18n5-57/+61
2014-10-22Fix crash when switching monitorsEugene Kilachkoff1-0/+7
When switching monitors AND displaying notifications at the same time, a rare situation might occur when notification window will be added to two or more stacks. One of the stacks will be removed soon enough, but the "destroy" handler will persist and will be triggered when the window disappears. This results in a reference to a freed memory and (usually) a daemon crash, a typical one is https://retrace.fedoraproject.org/faf/reports/359836/ for example. So, the removal handlers referring to a deleted stack must be cancelled prior to removal. Closes https://github.com/mate-desktop/mate-notification-daemon/pull/34
2014-10-02don't draw pie if timeout is zeroDenis Gorodnichev2-0/+6
Closes https://github.com/mate-desktop/mate-notification-daemon/pull/38
2014-10-01coco: Show actions boxStefano Karapetsas1-2/+0
Closes https://github.com/mate-desktop/mate-notification-daemon/issues/37
2014-07-12Sync translations with transifexmate-i18n7-55/+238
2014-07-03Use g_object_unref in callback for both Gtk+ versionsinfirit3-16/+0
2014-07-03Cleanup GTK_CHECK_VERSION and unify code where possibleinfirit6-224/+24
* Use GtkAllocation for both Gtk+ versions, added in 2.18 * Bump gdk-pixbuf required to 2.22 (release 2010) * GDK_DISPLAY_XDISPLAY | Since always * gdk_display_get_default | Since 2.22 * gdk_window_get_screen | Since 2.24 * gtk_widget_get_window | Since 2.14
2014-07-03Use gtk_widget_get_visible for both Gtk+ versionsinfirit4-25/+9
Also fix a bug in add_notification_action in coco-theme
2014-07-02Remove support for GTK2 < 2.20Stefano Karapetsas1-7/+2
2014-07-02Bump minimum GLIB and GTK2 versionsStefano Karapetsas1-7/+4
2014-06-27Merge pull request #33 from quark-zju/fix-wnck-workspace-nullmate-notification-daemon-1.9.0Stefano Karapetsas1-0/+5
Fix assertion WNCK_IS_WORKSPACE
2014-06-27Fix assertion WNCK_IS_WORKSPACEJun Wu1-0/+5
Some window manager such as i3-wm may cause wnck_screen_get_active_workspace to return NULL. Add a sanity check before using the return value.
2014-03-23Bump version to 1.9.0Stefano Karapetsas2-1/+4
2014-03-23Sync translations with transifexStefano Karapetsas3-28/+207
2014-03-01Bump version to 1.8.0mate-notification-daemon-1.8.0Stefano Karapetsas2-2/+2
2014-03-01Sync translations with transifexStefano Karapetsas3-0/+358
2014-02-23Sync translations with transifexStefano Karapetsas3-17/+19
2014-02-18Bump version to 1.7.90mate-notification-daemon-1.7.90Stefano Karapetsas2-2/+2
2014-02-18Update NEWSStefano Karapetsas1-0/+2
2014-02-18Rename NEWS -> NEWS.GNOMEStefano Karapetsas1-0/+0
2014-02-18configure: Add check-newsStefano Karapetsas1-1/+1
2014-02-18Sync translations with transifexStefano Karapetsas8-17/+915
2014-01-19Fix configure script with GTK3Stefano Karapetsas1-1/+1
Closes #29 https://github.com/mate-desktop/mate-notification-daemon/issues/29
2014-01-18Really fix build with latest mate-commonmate-notification-daemon-1.7.1Stefano Karapetsas1-2/+1
2014-01-18Fix build with latest mate-commonStefano Karapetsas1-2/+1
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-21 03:49:36 +0000