This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project wmaker-crm.git.

The branch, next has been updated
       via  cd7edbcc11a8b180dccdd584106c87736f9bcb3b (commit)
      from  f97b997f382f466e40c851575bbb971f64db2d3b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://repo.or.cz/w/wmaker-crm.git/commit/cd7edbcc11a8b180dccdd584106c87736f9bcb3b

commit cd7edbcc11a8b180dccdd584106c87736f9bcb3b
Author: Iain Patterson <[email protected]>
Date:   Fri Jun 22 17:03:59 2012 +0100

    Correct window shading logic.
    
    Fons Adriaensen reported that:
    
    > WM's 'unshade' seems to use multiple Expose events [...] even when
    > all animations and 'superfluous effects' are disabled.
    
    Typo in shade_animate() could cause windows to be animated when the
    no_animations preference was set. With this patch I see fewer
    XMoveWindow() calls and quicker shading.

diff --git a/src/actions.c b/src/actions.c
index 61be535..fed1c1e 100644
--- a/src/actions.c
+++ b/src/actions.c
@@ -1892,7 +1892,7 @@ static void shade_animate(WWindow *wwin, Bool what)
        int y, s, w, h;
        time_t time0 = time(NULL);
 
-       if (wwin->flags.skip_next_animation && wPreferences.no_animations)
+       if (wwin->flags.skip_next_animation || wPreferences.no_animations)
                return;
 
        switch(what) {

-----------------------------------------------------------------------

Summary of changes:
 src/actions.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


repo.or.cz automatic notification. Contact project admin [email protected]
if you want to unsubscribe, or site admin [email protected] if you receive
no reply.
-- 
wmaker-crm.git ("The Window Maker window manager")


-- 
To unsubscribe, send mail to [email protected].

Reply via email to