On Fri, 02 May 2014 19:22:39 +0100
Neil Roberts n...@linux.intel.com wrote:
Hi,
Currently Weston has a problem that it always puts new surfaces on the
same output as the one the first pointer is in. I guess the idea is
that most of the time surfaces are created as a result of mouse
events
We solved this under X11 with the startup-notification protocol. Ryan
Lortie has been looking at making a DBus-only startup-notification for
other platforms like Wayland.
Since there's an intersection here, I'm going to CC Ryan and have him
provide his thoughts on this, so we don't have duplicate
Hi,
Currently Weston has a problem that it always puts new surfaces on the
same output as the one the first pointer is in. I guess the idea is that
most of the time surfaces are created as a result of mouse events and
there is usually only one pointer so it works most of the time. However
of
Two comments on the proposal:
1. It would seem more useful for the desktop shell to send some info
about how the client was launched in environment variables. The client
may want to do other reactions besides just placing it's window, and
this will work for clients that do not want to use the
Bill Spitzak spit...@gmail.com writes:
1. It would seem more useful for the desktop shell to send some info
about how the client was launched in environment variables.
Yes, maybe it would be cleaner to agree on some protocol for the parent
process to send the information directly to the child.
On 05/02/2014 03:49 PM, Neil Roberts wrote:
1. It would seem more useful for the desktop shell to send some info
about how the client was launched in environment variables.
Yes, maybe it would be cleaner to agree on some protocol for the parent
process to send the information directly to the
