[winswitch] How does Xpra handle input and windowing?

Antoine Martin antoine at nagafix.co.uk
Sun Dec 4 10:13:26 GMT 2011

On 12/04/2011 04:44 AM, Eric Appleman wrote:
> Thanks for the response.
> Actual framerate is great. Perceived framerate sill isn't. The reason I
> want to use a different compositor is because I want vsync.
Making xpra vsync-aware should be possible but I am not sure how hard it
would be. (you will not be able to use xpra with another compositor)
OTOH, the server side would require setting the backing pixel data as
copy-on-write on each vsync, and always using the previous copy.
For the client side, I'm not sure what can/needs-to be done.


> As for my original question, a few more points I'd like to flesh out.
>  * Does Wimpiggy get used or is that separate?
It does get used, it provides the low-level window management bits.
>  * Input drivers on server X are overridden by dummy cursor, correct?
>  * How does Xpra isolate attached windows from their root window?
I'm not sure what you mean by "isolate".

> - Eric
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users

More information about the shifter-users mailing list