Re: [PATCH] rrcrtc: brackets are hard, lets go shopping.

2014-05-03 Thread Aaron Plattner
On 07/29/2013 08:19 PM, Dave Airlie wrote: Slaving two outputs on a secondary GPU to a primary GPU testing picked this up, in that we'd try to resize to the totally the wrong thing, then as usual segfault in the rotation code. This never got applied, did it? Reviewed-by: Aaron Plattner Sign

Re: [PATCH v2 1/2] ephyr: allow starting window at other than 0, 0 location (via kdrive -origin option)

2014-05-03 Thread Laércio de Sousa
Em 03/05/2014 14:02, "Keith Packard" escreveu: > You should use XParseGeometry or even XWMGeometry. If you want to avoid > Xlib, you should hack those functions into something that could be > included in an xcb utility library (probably util-wm). > > I couldn't find anything suitable in xcb yet, b

Re: [PATCH v2 1/2] ephyr: allow starting window at other than 0, 0 location (via kdrive -origin option)

2014-05-03 Thread Keith Packard
Laércio de Sousa writes: > OK. One last question: for negative values, should it support WxH-X-Y > syntax (harder to implement) or just WxH+-X+-Y syntax (easier to > implement)? You should use XParseGeometry or even XWMGeometry. If you want to avoid Xlib, you should hack those functions into som

Re: [PATCH v2 1/2] ephyr: allow starting window at other than 0, 0 location (via kdrive -origin option)

2014-05-03 Thread Laércio de Sousa
Em 02/05/2014 14:50, "Keith Packard" escreveu: > > Laércio de Sousa writes: > > > Some time ago I submitted another patch with the following approach: extend > > kdrive -screen option parsing to include strings like WxH+X+Y, and then > > place Xephyr window top-left corner at (X,Y). Do you think