Hi Wayland devs,
I'm currently implementing the pointer-constraints protocol and run into
a
small uncertainty with the documentation.
For zwp_locked_pointer_v1::set_region we have: "The new lock region is
double-
buffered. The new lock region will only take effect when the associated
surface
etc. etc. I think this is one of the strong
points of NETWM and completely missing here.
* a mechanismn like startup notification/_NET_WM_USER_TIME: a compositor would
probably want to know when a surface got created due to user interaction for
focus stealing prevention
Best Regards
Ma
n Mon, Nov 18, 2013 at 2:47 AM, Thiago Macieira
>
> wrote:
> > On segunda-feira, 18 de novembro de 2013 08:20:37, Martin Gräßlin wrote:
> > > I'm afraid that exactly that will happen then and I think it's the
> >
> > shell's
> >
> > > r
On Sunday 17 November 2013 22:27:29 Thiago Macieira wrote:
> On segunda-feira, 18 de novembro de 2013 06:37:47, Martin Gräßlin wrote:
> > That sounds look a good solution to me!
>
> Make it simpler: all clients MUST be able to draw decorations. That's what
> Wayland up un
On Sunday 17 November 2013 22:54:47 Thiago Macieira wrote:
> Applications that do not negotiate must figure out the proper decoration on
> their own. It's not the compositor's job to enforce the style. If the
> application then looks out of place, it's the application's fault, not the
> compositor'
On Saturday 16 November 2013 11:32:50 you wrote:
> On Nov 15, 2013 5:27 AM, "Martin Gräßlin" wrote:
> > Hi all,
> >
> > this is a reply to the topic of whether to have information about
>
> decorations
>
> > in the xdg_shell at all (see [1]). Sor
in shells, which prefer to not have them.
Also it doesn't force CSD applications to support it. They could just announce
that they do CSD no matter what.
Opinions? Would that be acceptable for everybody?
Cheers
Martin Gräßlin
[1]
http://lists.freedesktop.org/archives/wayland-devel/2