On Mon, Oct 05, 2015 at 12:24:19PM -0500, Derek Foreman wrote:
> On 02/10/15 07:20 AM, David FORT wrote:
> > This is required if we want to correctly remove a wl_seat compositor-side. A
> > wl_seat is announced as a global object, then it is bound by the client.
> > When
> > the compositor wants
On Mon, Oct 05, 2015 at 12:24:19PM -0500, Derek Foreman wrote:
> On 02/10/15 07:20 AM, David FORT wrote:
> > This is required if we want to correctly remove a wl_seat compositor-side. A
> > wl_seat is announced as a global object, then it is bound by the client.
> > When
> > the compositor wants
On 02/10/15 07:20 AM, David FORT wrote:
> This is required if we want to correctly remove a wl_seat compositor-side. A
> wl_seat is announced as a global object, then it is bound by the client. When
> the compositor wants to remove the seat, it shall announce the global removal
> of
> the object.
This version takes in account last Jonas Ådahl's remarks.
David FORT (1):
wayland: add a release request on wl_seat
protocol/wayland.xml | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
--
1.9.1
___
wayland-devel mailing list
This is required if we want to correctly remove a wl_seat compositor-side. A
wl_seat is announced as a global object, then it is bound by the client. When
the compositor wants to remove the seat, it shall announce the global removal of
the object. The client can then call the release request on
On Wed, Sep 30, 2015 at 10:17:49PM +0200, David FORT wrote:
> This is required if we want to correctly remove a wl_seat compositor-side. A
> wl_seat is announced as a global object, then it is bound by the client. When
> the compositor wants to remove the seat, it shall announce the global removal
This is required if we want to correctly remove a wl_seat compositor-side. A
wl_seat is announced as a global object, then it is bound by the client. When
the compositor wants to remove the seat, it shall announce the global removal of
the object. The client can then call the release request on
