Hi. I'm afraid that notification windows and tooltips are quite similar.
I've built tooltip on toytoolkit using set_transient surface type, using
the inactive method (for not giving focus on it). So instead creating a
new surface type for notification windows, I think you can create a
dummy surface with output's size, create transient surface on it
(set_transient) and setting as inactive. Then for its configuration
(corner, order, etc), instead relying on the config file, we'd need to
create transient methods on the protocol for dealing with it (just like
the 'inactive') so windows could be configured independently. I guess
this gives a cleaner solution.
Tiago
On 12/26/2012 03:59 PM, Quentin Glidic wrote:
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.
---
protocol/wayland.xml | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 0ce68ef..199f14f 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -527,7 +527,7 @@
</request>
</interface>
- <interface name="wl_shell_surface" version="1">
+ <interface name="wl_shell_surface" version="2">
<description summary="desktop style meta data interface">
An interface implemented by a wl_surface. On server side the
@@ -729,6 +729,16 @@
to the client owning the popup surface.
</description>
</event>
+
+ <!-- Version 2 additions -->
+
+ <request name="set_notification">
+ <description summary="make the surface a notification surface">
+ 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.
+ </description>
+ </request>
</interface>
<interface name="wl_surface" version="2">
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
