My application attaches a XFixes created reactangle to a window.
Therefore it does a XOpenDisplay() + XFixesCreateRegion() +
XCloseDisplay() inside one short function and done.
After the above outlined function resturns a call to XFixesFetchRegion()
from a outside observer forces the
Common sense (and the fact that the error says BadRegion here) suggest that
reg = XFixesCreateRegion( display, rec, 1);
This region number is no longer valid after you close the display.
Doing this a 2nd time after setting nRect = 0 will fix it.
Maarten.
Am 23.06.09, 11:35 +0200 schrieb Maarten Maathuis:
Common sense (and the fact that the error says BadRegion here) suggest that
reg = XFixesCreateRegion( display, rec, 1);
This region number is no longer valid after you close the display.
Doing this a 2nd time after setting nRect = 0 will
Please don't think i know what you are actually trying to do, i solved
this like you would a puzzle. First guess happened to work.
Maarten.
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
And this region is some property of the root window?
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Kai-Uwe Behrmann k...@gmx.de writes:
My application attaches a XFixes created reactangle to a window.
Therefore it does a XOpenDisplay() + XFixesCreateRegion() +
XCloseDisplay() inside one short function and done.
After the above outlined function resturns a call to XFixesFetchRegion()
from
Am 23.06.09, 13:10 +0200 schrieb Eirik Byrkjeflot Anonsen:
Kai-Uwe Behrmann k...@gmx.de writes:
Any idea how to avoid a quit from XFixesFetchRegion()? A error message
would be enough. A exit in not acceptable to the application.
My memory is rather unclear on this point, but if the default
