Peter Hutterer a5e6af5bff eis: after the client binds the seat, drop the capabilities ... This way eis_seat_has_capability() returns the effective capabilities the server can actually use - no point creating touch devices when the client has not confirmed that. In theory we should have a eis_seat_get_effective_capabilities() to differ between configured and effective capabilities, but I'm having a hard time thinking of a use-case where the implementation forgets which caps it enabled. The side-effect of this patch is that adding a device without capabilities requested by the client now produces warning.		2022-03-07 11:21:36 +10:00
..
buildtest.c	Add SPDX identifiers to all source files	2022-03-03 00:27:36 +00:00
buildtest.cc	Add C++ header guards	2020-09-29 17:30:49 +10:00
eierpecken.c	ei: require the client to confirm capabilities rather than drop them	2022-03-07 11:02:35 +10:00
eierpecken.h	test: add test cases for eis -> ei events	2022-03-04 14:04:33 +10:00
test-ei-device.c	test: add test cases for eis -> ei events	2022-03-04 14:04:33 +10:00
test-ei-seat.c	ei: require the client to confirm capabilities rather than drop them	2022-03-07 11:02:35 +10:00
test-ei.c	Add concept of active/passive libei contexts	2022-03-04 14:04:33 +10:00
test-eis.c	eis: after the client binds the seat, drop the capabilities	2022-03-07 11:21:36 +10:00
test-main.c	Add SPDX identifiers to all source files	2022-03-03 00:27:36 +00:00
unit-tests.c	Add SPDX identifiers to all source files	2022-03-03 00:27:36 +00:00