romangg added a comment.
I believe it works like this: A seat has one global pointer, one global keyboard and one global touch "object" each. But clients can bind to them multiple times. That's why there are focus.pointers and focus.keyboards vectors although there is only one global pointer/keyboard. A different question is what happens on a multi-seat system: when there are several mice or keyboards, the compositor must support splitting them up to multiple seats (but every seat again has only one global keyboard and pointer object). This does not work of course for touch screens, so that's why the specs is reads differently here. But as said this is not directly related to focus.pointers, focus.keyboards or focus.touchs being vectors per seat or not. REPOSITORY R127 KWayland REVISION DETAIL https://phabricator.kde.org/D15443 To: romangg, #kwin, #frameworks Cc: davidedmundson, kde-frameworks-devel, michaelh, ngraham, bruns
