On Wed, 2016-09-14 at 14:01 -0400, Stirling Westrup wrote:
> I'm currently reading through the source for the damage extension in
> damage.c and I noticed that the list of functions that get wrapped
> when a screen gets damage support is not the same as the list of
> functions that get unwrapped wh
I'm currently reading through the source for the damage extension in
damage.c and I noticed that the list of functions that get wrapped when a
screen gets damage support is not the same as the list of functions that
get unwrapped when the screen is closed. That is DamageSetup() wraps these
function
On 09/11/2016 08:29 PM, Nathan Schulte wrote:
> I'm using X.org w/ Debian Sid:
>
>> nmschulte@desmas-l:~$ Xorg -version
>>
>> X.Org X Server 1.18.4
>> Release Date: 2016-07-19
>> X Protocol Version 11, Revision 0
>> Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
>> Current Operating Sy
Hello,
XRestackWindows function :
It is said in
https://www.x.org/releases/X11R7.7/doc/libX11/libX11/libX11.html#Changing_Window_Stacking_Order
:
"For each window in the window array that is not a child of the
specified window, a BadMatch error results."
but in ftp://www.x.org/pub/X11R7.7
