On Dec 3, 2012, at 9:19 AM, Tiago Vignatti wrote:
> as I said, the X server has two protocol streams in which messages cannot be
> ordered. Say that ConfigureNotify (via X11) arrives in xwm, the compositor
> might already have tried to map the X client content surface on screen
> because it go
On 11/30/2012 10:01 PM, Bill Spitzak wrote:
Tiago Vignatti wrote:
The approach used here shows a weakness of the Weston WM-as-client
architecture: one cannot guarantee that the X11 stream needed to create
windows with its right position will happen before Weston maps the
surface,
via Wayland. I
Tiago Vignatti wrote:
The approach used here shows a weakness of the Weston WM-as-client
architecture: one cannot guarantee that the X11 stream needed to create
windows with its right position will happen before Weston maps the surface,
via Wayland. IOW we'd like always ConfigureNotify with the
This patch solves the window positioning problem through forwarding its global
coordinates to X. A change in desktop-shell protocol is needed for doing so
and to add a new type of surface, the xwayland (description and details of it
are on the previous commit and also in the protocol).
The approac
