This interface is designed to be bound only once by a notification
daemon.
Notification surfaces are special surfaces that the user should
always be able to see. The compositor is in charge of displaying
them to be visible without disturbing the user workflow.
Signed-off-by: Quentin Glidic
---
On 21/01/2013 19:53, Casey Dahlin wrote:
> Is there a reason to do this in wayland protocol rather than the already
> established freedesktop method over DBus?
The fd.o specification provides a protocol to notify the user, using a
(hopefully) desktop-integrated daemon. The Wayland interface I’m ad
On Sun, Jan 20, 2013 at 07:16:09PM +0100, Quentin Glidic wrote:
> This interface is designed to be binded only once by a notification
> daemon.
>
> Notification surfaces are special surfaces that the user should
> always be able to see. The compositor is in charge of displaying
> them to be visibl
On Sun, Jan 20, 2013 at 12:16 PM, Quentin Glidic
wrote:
> This interface is designed to be binded only once by a notification
> daemon.
Should we have an error enum for "interface already bound". That way
the compositor can do something useful if two clients try to bind at
the same time. Also,
This interface is designed to be binded only once by a notification
daemon.
Notification surfaces are special surfaces that the user should
always be able to see. The compositor is in charge of displaying
them to be visible without disturbing the user workflow.
---
This interface should be bindin
