Skip to content

Drop mentions of capability monitoring

Peter Hutterer requested to merge whot/libei:wip/drop-monitoring into master

The original idea here was that a libei client could request the Pointer capability to be notified of any pointer movements, thus providing a simple way to capture input for the synergy use-case.

This is a can of worms better left untouched. How input events are captured and what information is available is quite specific to the display server, let alone the triggers for when it needs to start and stop. To have that in libei requires something like triggers ("start when pointer hits the edge") which again opens a new can of worms. Which seat are we referring to? What is a screen edge? How about shortcuts?

Receiving input events can be handled by libeis anyway: any EIS server is capable of receiving input events by definition so the capability monitoring could be solved by making the capturing compositor a libei client and the other process an EIS server. i.e. the circle is closed with:

[compositor|libei] -> [EIS|synergy-client]
                               ||
	                  [synergy-server|libei] -> [EIS|compositor]

cc @ofourdan

Merge request reports