Mike Small <[email protected]> writes: > -> Next is where wc's members get their values, but two of them > -> (namely .sibling and .stack_mode) are not set so will have fairly > unpredictable > -> values. No doubt when you run you happen to get a zero for > -> wc.stacking_mode, which corresponds to Above. I get 1, corresponding to > -> Below. If you try my steps again, but instead put my test program window > -> on the bottom and click on a corner hanging out from under, my guess is > -> that you'll see nothing happen. But if you look at my code you can see > -> that clicking on the window should make it request a raise in the > -> stacking order.
This is mixed up. You would have to change the test program to make a lower request and then click on the window while it is on top. -- Mike Small [email protected]
