charly4711
November 23rd, 2007, 08:10 AM
Hi there,
sorry for crossposting, but since I didn't get any kind of answer in the AppDev forum (not even: "no way to make this work", or "this is an FAQ"), I think perhaps this is the better audience, even if it is not directly concerning compiz core itself.
...
I'm working on this application that relies on Xdamage events for notification about screen changes.
It seems compiz (and beryl, and prolly any other compositing window mgr.) breaks the contract that (1) getting the event, (2) subtracting the damage, and (3) XSync'ing the display ensures the change will actually have been painted on screen. The change may appear on screen at some later time (depending on animation) and may occur in areas well outside the damaged rectangle.
While I'm wondering whether it's good to break that contract, is there any other way for an application external to compiz to retrieve the information about areas on-screen which have changed and have those changes already painted?
TIA,
Karl.
sorry for crossposting, but since I didn't get any kind of answer in the AppDev forum (not even: "no way to make this work", or "this is an FAQ"), I think perhaps this is the better audience, even if it is not directly concerning compiz core itself.
...
I'm working on this application that relies on Xdamage events for notification about screen changes.
It seems compiz (and beryl, and prolly any other compositing window mgr.) breaks the contract that (1) getting the event, (2) subtracting the damage, and (3) XSync'ing the display ensures the change will actually have been painted on screen. The change may appear on screen at some later time (depending on animation) and may occur in areas well outside the damaged rectangle.
While I'm wondering whether it's good to break that contract, is there any other way for an application external to compiz to retrieve the information about areas on-screen which have changed and have those changes already painted?
TIA,
Karl.