Displaying 3 results from an estimated 3 matches for "findsiblingbelow".
2007 Nov 21
1
window stacking bug #1
...he "show widgets" shortcut.
This means the widgets are invisible, unless the full-screen window is
transparent. (Note that the window is correctly "shaded".
****
I took a look at the source, and the problem seems to be in
src/window.h, function raiseWindow(). The function uses
findSiblingBelow (w, FALSE) to position the window it's called on,
where the FALSE parameter means that the sibling (on top of which the
window is moved) cannot be a full-screen window. The result is that if
the topmost window is full-screen, calling raiseWindow() on a window
will leave it hidden.
In the case...
2007 Nov 21
0
window stacking bug #2
...to set the window's (initial) stacking, among
other things. For instance, at one point it runs:
if (stackingMode != CompStackingUpdateModeNone)
{
Bool aboveFs;
aboveFs = (stackingMode == CompStackingUpdateModeAboveFullscreen);
mask |= addWindowStackChanges (w, &xwc, findSiblingBelow (w, aboveFs));
}
which raises the given window on top of everything if the stacking
mode is CompStackingUpdateModeAboveFullscreen. So newly-created
windows are placed below full-screen ones, because they're not
mentioned in that test. This might seem like a good idea, except that
they'...
2008 Feb 07
1
[ANNOUNCE] compiz-0.7.0
...ation update (closes #13094)
Don't restack ancestors on initial map.
Factor out retrieving the highest valid sibling under a given window
into a separate function.
Move restacking due to focus stealing prevention to
updateWindowAttributes function.
The sibling found by findSIblingBelow might already be the active
window, so include it in check.
The display dbus path is now "display", no longer "allscreens".
Wrap setOptionForPlugin function.
Fix typos.
Fix dbus paths (shadow_offset_x/y -> shadow_x/y_offset).
Avoid possible dere...