Re: wayland-protocols scope and governance

2019-06-19 Thread Jonas Ådahl
On Tue, Jun 18, 2019 at 07:31:47PM -0400, Drew DeVault wrote: > On Mon Jun 17, 2019 at 9:55 AM Jonas Ådahl wrote: > > > a. Namespaces are implemented in practice by prefixing each interface > > > name in a > > >protocol definition (XML) with the namespace name, and an underscore > > > (e.g.

Multiple touchscreen environment with Weston

2019-06-19 Thread Theo BUENO
Hello everyone, I am (relatively) new Weston user working with industrial embedded Linux systems. I am seeking for advice regarding a Weston use case. I have been trying to understand how would one map touchscreens to unique displays on a system which has several touchscreen displays. It is my

[PATCH] xdg-shell: remove constraints for fullscreen

2019-06-19 Thread Drew DeVault
Compositors are free to render surfaces at their discretion. This change clarifies that for xdg-shell's fullscreen surfaces. --- This point has been a recurring cause for frustration in Sway development, as users expect windows beneath transparent fullscreen windows to be shown. The main use-case

Re: wayland-protocols scope and governance

2019-06-19 Thread Jonas Ådahl
On Wed, Jun 19, 2019 at 10:52:32AM -0400, Drew DeVault wrote: > On Wed Jun 19, 2019 at 8:38 AM Jonas Ådahl wrote: > > > I'm okay with this definition, but I'll again mention that this wording > > > makes a clear case for the wlr toplevel management protocol: > > > > > >

Re: [PATCH] xdg-shell: remove constraints for fullscreen

2019-06-19 Thread Jonas Ådahl
On Wed, Jun 19, 2019 at 01:35:42PM -0400, Drew DeVault wrote: > Compositors are free to render surfaces at their discretion. This > change clarifies that for xdg-shell's fullscreen surfaces. > --- > This point has been a recurring cause for frustration in Sway > development, as users expect