Add key_state and button_state enums

Rather than hardcoding 0 and 1 everywhere.

Signed-off-by: Daniel Stone <daniel@fooishbar.org>
This commit is contained in:
Daniel Stone 2012-05-30 16:31:48 +01:00 committed by Kristian Høgsberg
parent 9a1705c5f5
commit 872d074a43
3 changed files with 30 additions and 6 deletions

View file

@ -818,6 +818,15 @@
<arg name="surface_y" type="fixed"/>
</event>
<enum name="button_state">
<description summary="physical button state">
Describes the physical state of a button which provoked the button
event.
</description>
<entry name="released" value="0" summary="button is not pressed"/>
<entry name="pressed" value="1" summary="button is pressed"/>
</enum>
<event name="button">
<description summary="pointer button event">
Mouse button click and release notifications. The location
@ -862,6 +871,16 @@
<arg name="surface" type="object" interface="wl_surface"/>
</event>
<enum name="key_state">
<description summary="physical key state">
Describes the physical state of a key which provoked the key event.
When a key repeats, the sequence is down -> repeat -> repeat -> up.
</description>
<entry name="released" value="0" summary="key is not pressed"/>
<entry name="pressed" value="1" summary="key is pressed"/>
<entry name="repeat" value="2" summary="key is pressed and repeating"/>
</enum>
<event name="key">
<description summary="key event">
A key was pressed or released.