summaryrefslogtreecommitdiff
path: root/src/gs-fade.c
AgeCommit message (Collapse)AuthorFilesLines
2018-05-14Fixed some gdk deprecationsyetist1-1/+3
2017-01-17GTK+3.22: fix some GdkScreen related deprecationsAlexei Sorokin1-4/+4
2016-11-20move to GTK+3 (>= 3.14), drop GTK+2 code and --with-gtk build optionmonsta1-184/+0
and require libmatekbd and libmate-desktop >= 1.17
2016-06-18Gtk3: fix several deprecationsSorokin Alexei1-8/+154
2015-12-11drop some unused variablesWolfgang Ulbrich1-2/+1
taken from: https://git.gnome.org/browse/gnome-screensaver/commit/?id=214ab95 https://git.gnome.org/browse/gnome-screensaver/commit/?id=4f0124a
2015-09-16manager: fade out explicitly locks more quicklyRay Strode1-1/+1
If the screensaver is explicitly asked to lock (as opposed to locking because of idle), then we should do it very quickly. 1 second is too long. This commit changes the fade to 60 steps per second and a quarter of second long (put another way, about 15 fade increments). Taken from gnome-screensaver, commit:44edc03104f9757f4d866f24df8793f064b6ce70 And applied to MATE by infirit
2015-07-09Always use GDK_DISPLAY_XDISPLAY instead of GDK_DISPLAYinfirit1-28/+0
Has been in Gtk since 2.22
2014-11-30Update to api changes for MateRR* in mate-desktopinfirit1-3/+1
2014-07-21Prevent SegFault in the absence of XRANDRDavid Tagatac1-1/+2
(Fix #46) Patch by Steven Chamberlain https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=bug749629.patch;att=1;bug=749629
2013-11-12Add GTK3 supportStefano Karapetsas1-1/+29
2012-11-18fixed incorrect fsf addressesSteve Zesch1-1/+1
2011-11-04first commitPerberos1-0/+987