I'm not sure the best way to go about reporting this but I've filed the
following bug report against mesa:
https://bugs.freedesktop.org/show_bug.cgi?id=44919
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/m
Pekka Paalanen wrote:
Unmapped surfaces never occlude anything, since they are invisible. In
your case, if you first raise W, then map B, you might see a full W,
and then B appearing on top of it. No any other surface content can
flash inside W. Is the temporary showing of full W before B appear
The decorations were not responding, could not move or resize the
dialog, and it painted with a black shade.
When the dialog is created, schedule a resize instead of a repaint. The
resize will initialise the widget tree, and let everything draw and work
as it should.
Signed-off-by: Pekka Paalanen
I noticed that gears may sometimes stop, and then start animating
again. Turned out the underlying problem is a known one,
eglSwapBuffers() dispatching Wayland events.
The patch below is a nice try, but it creates exactly the problem the
comment warns about. It is very difficult to open the window
On Tue, 17 Jan 2012 10:36:03 -0800
Bill Spitzak wrote:
> On 01/17/2012 02:32 AM, Pekka Paalanen wrote:
>
> > I think we already have the unmapped feature. In Wayland terms:
> >
> > 1. A client creates a surface.
> > The surface is initially unmapped, and not visible.
> >
> > 2. The client se
