1. Confirmed the shifted window regression is now fixed. Seems to work without any obvious bugs now.
2. I'm not entirely sure about replacing geometry with serverGeometry. I thought it would be a good idea to do the opposite. There would be a slight performance penalty, but using just "geometry" would guarantee that compiz always agrees with the actual server geometry, instead of guessing/assuming that serverGeometry is accepted by the server (which does not always seem to be true, hence bug 886192).
3. There are two instances of double semicolons ";;" in this proposal.
4. I suspect this proposal will conflict just slightly with the proposal for bug 940139. But it should be minor.
1. Confirmed the shifted window regression is now fixed. Seems to work without any obvious bugs now.
2. I'm not entirely sure about replacing geometry with serverGeometry. I thought it would be a good idea to do the opposite. There would be a slight performance penalty, but using just "geometry" would guarantee that compiz always agrees with the actual server geometry, instead of guessing/assuming that serverGeometry is accepted by the server (which does not always seem to be true, hence bug 886192).
3. There are two instances of double semicolons ";;" in this proposal.
4. I suspect this proposal will conflict just slightly with the proposal for bug 940139. But it should be minor.
5. NEW REGRESSION:
375 - XSynchronize (dpy, synchronousX ? True : False);
376 +// priv->connection = XGetXCBConnection (priv->dpy);
6. Why always two spaces before "* 2" ?