Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
and revert "GTK 3.21: Fix background changing, startup delay".
These are no longer of need as Caja reclaimed its ability to draw backgrounds.
|
|
and require libmatekbd and libmate-desktop >= 1.17
|
|
that function is only called with GTK+ < 3.22
|
|
|
|
Fix background changing with or without caja running. Remove all references to Caja from GTK 3.21 or later builds, remove resulting unused variable.
|
|
Make sure m-s-d knows to draw the background unconditionally when used with transparent version of Caja for GTK 3.21.3 or later
|
|
|
|
|
|
g_list_nth_data just returns NULL if either list or element is NULL
Closes https://github.com/mate-desktop/mate-settings-daemon/pull/91
|
|
|
|
|
|
|
|
Namely:
1. In caja_is_drawing..(), only get atom for WM_CLASS property if it exists.
2. Cache gsettings draw-background & show-desktop-icons key-values, and only update
when either actually changes, to avoid unnecessary queries to the dconf-service.
3. Avoid conflicts between settings_change_event_cb() & on_bg_handling_changed().
4. Keep track of screen sizes, to ensure size actually changed when signalled, to
avoid double-redraw on an extraneous signal, which can lockup the daemon, because
we draw immediately (w/out g_idle_add). Though we don't fade in re-draws triggered
by size/monitors-changed signals, making all re-draws queued causes issues with
fading, when we do fade (on bg change), and queueing is unnecessary here anyway.
5. Track a redraw in progress, to avoid any possible (and unforseeable) clashes.
|
|
|
|
|
|
Observe new mate-bg (global) fade option, via do_crossfade_background()
Change dont_draw_background() to a do_, to avoid double-negative like !dont.
|
|
from 24 -> 20, to account for 'nautilus' -> 'caja' change (4 bytes less).
|
|
hopefully to avoid taking over background-drawing when Caja is doing it.
|
|
Because we should handle the background drawing when either:
- "draw-background" is re-enabled, or
- "show-desktop-icons" is disabled.
N.B.
We may still need to consider this issue, which was never resolved in gnome,
because they stopped auto-launching nautilus & removed it from 3.0 sessions:
Nautilus registers with the session before it's ready.
https://bugzilla.gnome.org/show_bug.cgi?id=568588
Would also be wise to import the (recent) changes made in the bug below:
Provide a singleton SessionManager proxy object
https://bugzilla.gnome.org/show_bug.cgi?id=686556
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=564909
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=da9bd9769caa0f776edf5636c6ae09ba425d6f6e
|
|
prevents some strange flicker when quickly selecting multiple backgrounds
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5cb80995b6899c6ed185797333b709ea9342de42
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=34d6831d7bf5fdf869f1b4802d8920c4a90825db
|
|
and use new mate-bg API ("show-desktop-icons")
For reference, see:
Port backround module to GSettings
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=23b50dfc7078b78a513598060ee22ae46c262534
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=c9d62bab8acb166aa720fa5d0356657177be6be5
background: always check if Nautilus is running
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d22b75db508a792e3786a2011b707e930a0f0355
background: reintroduce GnomeBg "changed" signal
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d7a6f707c9e6f924fea7565967d9c5c1ad8b1533
background: Listen to screen changes only after GnomeBg is constructed
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d6d12b643aeec91fa3d1ed19104f1c0d1ded7870
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d38bb683005b71f3bf483aafee2f7c36d800a0c7
|
|
|
|
|
|
|
|
(https://github.com/mate-desktop/mate-desktop/issues/16)
|
|
(http://imageshack.us/photo/my-images/9/254223656580e542a60a.jpg/)
|
|
|