Peter Hutterer d17868303e Make the button mapping DBus API a single entry point ...

Instead of multiple entry points for different values, make the button mapping
a single entry point that takes the mapping type and a variant for the value.

The ratbagd.py bindings are basically left as-is.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

2019-02-27 12:07:25 +10:00

..

.gitignore

Merge ratbagd into libratbag

2017-06-29 14:59:13 +10:00

org.freedesktop.ratbag1.conf

ratbagd: move the source from ratbagd/src to just ratbagd/

2017-06-29 15:02:56 +10:00

ratbagd-button.c

Make the button mapping DBus API a single entry point

2019-02-27 12:07:25 +10:00

ratbagd-device.c

Drop the Device.Id from the DBus interface

2019-02-25 10:48:50 +01:00

ratbagd-led.c

Drop the Led.Type property

2019-02-22 10:09:17 +01:00

ratbagd-profile.c

Move the ReportRate into the profile

2019-02-27 11:31:59 +10:00

ratbagd-resolution.c

Drop the Resolution.Capabilities field

2019-02-27 11:44:05 +10:00

ratbagd-test.c

Move the ReportRate into the profile

2019-02-27 11:31:59 +10:00

ratbagd-test.h

ratbagd: split the test device out into a seprate file

2017-09-01 09:30:38 +02:00

ratbagd.8

ratbagd: move the source from ratbagd/src to just ratbagd/

2017-06-29 15:02:56 +10:00

ratbagd.c

Revert "ratbagd: pick the ID from a list of preselected names"

2019-02-25 10:48:50 +01:00

ratbagd.h

Revert "ratbagd: pick the ID from a list of preselected names"

2019-02-25 10:48:50 +01:00

ratbagd.service.in

Merge ratbagd into libratbag

2017-06-29 14:59:13 +10:00