inputproto: Changes to 'master'

[Peter Hutterer]

 XI2proto.h   |   15 ++++++++++-----
 XI2proto.txt |   36 +++++++++++++++++++++++++++---------
 configure.ac |    2 +-
 3 files changed, 38 insertions(+), 15 deletions(-)

New commits:
commit 3f0067b45e66ef8db785b67a36f015fd4e6a9f6c
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Thu Jun 18 00:29:44 2009 +1000

    XIDeviceChangedEvents may occur on master devices too.
    
    Prime example is a change in the number of buttons due to the availability
    of a new slave device.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

commit b40f48b15e3362cc7b5aeb800b7de072ce20e4aa
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Wed Jun 17 09:09:56 2009 +1000

    inputproto 1.9.99.12
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

commit a6edd59c440cae9cd8ac775bb4d67ab433f2aae3
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Wed Jun 17 08:53:26 2009 +1000

    Use the term 'labels' to refer to button and axes labels.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

commit b0f7e24d210cb6d0a1c47cae39b54e56a5e996d8
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Tue Jun 16 13:14:47 2009 +1000

    Include valuator value in XIValuatorClasses
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

commit b2fb9f81a2a7af8656309420facd58ab610d5da1
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Sun Jun 14 08:23:56 2009 +1000

    Include button state in XIButtonClasses.
    
    Without including the state in a button class, it is impossible to know the
    state of a device until this device has pressed or released another button
    (and thus sends an event).
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

commit db98b817355ed12609cff077c4a12948ac41f88d
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Sun Jun 7 17:51:04 2009 +1000

    Add a source field to the class information.
    
    In some cases it is required to know the source device of a particular
    device class. In the future we might also do lazy copying of classes,
    meaning that for a given device, each class may come from a different
    source. Hence the source id should be included for each class.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>