[PATCH] Wayland: Add how wl_keyboard represents more keyboards

[Martin Minarik]

This has been discussed.
If the user wants to be able to track multiple keyboards, they need
multiple seats.

The enter keys attribute means it's pressed on one or multiple
seat-attached keyboards. The keys never contains duplicate keys. 
---
 protocol/wayland.xml |   14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index f3ba296..36265fc 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -1384,7 +1384,8 @@
   <interface name="wl_keyboard" version="1">
     <description summary="keyboard input device">
       The wl_keyboard interface represents one or more keyboards
-      associated with a seat.
+      associated with a seat. The compositor acts as if there is one
+      keyboard.
     </description>
 
     <enum name="keymap_format">
@@ -1408,7 +1409,8 @@
     <event name="enter">
       <description summary="enter event">
 	Notification that this seat's keyboard focus is on a certain
-	surface.
+	surface. The keys are currently depressed on one or multiple
+	seat-attached devices. The keys contain no duplicate items.
       </description>
       <arg name="serial" type="uint"/>
       <arg name="surface" type="object" interface="wl_surface"/>
@@ -1429,15 +1431,17 @@
 
     <enum name="key_state">
       <description summary="physical key state">
-	Describes the physical state of a key which provoked the key event.
+	Describes the new state of a key which provoked the key event.
       </description>
       <entry name="released" value="0" summary="key is not pressed"/>
-      <entry name="pressed" value="1" summary="key is pressed"/>
+      <entry name="pressed" value="1" summary="key is pressed at least once"/>
     </enum>
 
     <event name="key">
       <description summary="key event">
-	A key was pressed or released.
+	A key was pressed first time or released the last time.
+	In case the same key code is, or has been held on multiple seat-attached devices,
+	no event is provoked.
         The time argument is a timestamp with millisecond
         granularity, with an undefined base.
       </description>
-- 
1.7.10.4