BitHeaven
/
picom
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove some spurious code 

If the window is fading out, then the new fade-in will execute the finish_unmap/destroy, and that will kill the pixmap already.
This commit is contained in:
Dana Jansens 2008-02-14 23:39:46 -05:00
parent 873402251a
commit c213ab27ff
1 changed files with 0 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
xcompmgr.c
View File

@ -1307,17 +1307,6 @@ map_win (Display *dpy, Window id, unsigned long sequence, Bool fade)
#endif #endif
w->damaged = 0; w->damaged = 0;
#if HAS_NAME_WINDOW_PIXMAP
/* If the window was previously mapped and its pixmap still exists, it
is out of date now, so force us to reacquire it. (If the window
re-maps before the unmap fade-out finished) */
if (w->pixmap)
{
XFreePixmap (dpy, w->pixmap);
w->pixmap = None;
}
#endif
if (fade && winTypeFade[w->windowType]) if (fade && winTypeFade[w->windowType])
set_fade (dpy, w, 0, get_opacity_percent (dpy, w), fade_in_step, 0, True, True); set_fade (dpy, w, 0, get_opacity_percent (dpy, w), fade_in_step, 0, True, True);
} }