{"action":"created","issue":{"url":"https://api.github.com/repos/i3/i3/issues/1799","labels_url":"https://api.github.com/repos/i3/i3/issues/1799/labels{/name}","comments_url":"https://api.github.com/repos/i3/i3/issues/1799/comments","events_url":"https://api.github.com/repos/i3/i3/issues/1799/events","html_url":"https://github.com/i3/i3/issues/1799","id":95756839,"number":1799,"title":"enhancement: Implement RandR 1.5 support","user":{"login":"stapelberg","id":55506,"avatar_url":"https://avatars.githubusercontent.com/u/55506?v=3","gravatar_id":"","url":"https://api.github.com/users/stapelberg","html_url":"https://github.com/stapelberg","followers_url":"https://api.github.com/users/stapelberg/followers","following_url":"https://api.github.com/users/stapelberg/following{/other_user}","gists_url":"https://api.github.com/users/stapelberg/gists{/gist_id}","starred_url":"https://api.github.com/users/stapelberg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stapelberg/subscriptions","organizations_url":"https://api.github.com/users/stapelberg/orgs","repos_url":"https://api.github.com/users/stapelberg/repos","events_url":"https://api.github.com/users/stapelberg/events{/privacy}","received_events_url":"https://api.github.com/users/stapelberg/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/i3/i3/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-07-17T22:26:11Z","updated_at":"2015-07-18T12:38:43Z","closed_at":null,"body":"See http://cgit.freedesktop.org/xorg/proto/randrproto/commit/?id=4109f29861a7066970a2afd079d0fc2c12828bcb for the spec changes.\r\n\r\nWe should evaluate whether i3 needs to understand the new concept of “monitors” — it is my understanding that we have to add support for it, otherwise we will misdetect tiled 4K displays (using Multistream Transport = MST), such as the Dell UP2414Q, as being multiple monitors instead of just one monitor.\r\n\r\nUnfortunately, AFAICT, not a single graphics driver supports RandR 1.5 yet, so ideally we’d find a different way of testing such a scenario. Maybe contacting Dave Airlie or Keith Packard and asking for test data (in which format?) would help."},"comment":{"url":"https://api.github.com/repos/i3/i3/issues/comments/122537450","html_url":"https://github.com/i3/i3/issues/1799#issuecomment-122537450","issue_url":"https://api.github.com/repos/i3/i3/issues/1799","id":122537450,"user":{"login":"stapelberg","id":55506,"avatar_url":"https://avatars.githubusercontent.com/u/55506?v=3","gravatar_id":"","url":"https://api.github.com/users/stapelberg","html_url":"https://github.com/stapelberg","followers_url":"https://api.github.com/users/stapelberg/followers","following_url":"https://api.github.com/users/stapelberg/following{/other_user}","gists_url":"https://api.github.com/users/stapelberg/gists{/gist_id}","starred_url":"https://api.github.com/users/stapelberg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stapelberg/subscriptions","organizations_url":"https://api.github.com/users/stapelberg/orgs","repos_url":"https://api.github.com/users/stapelberg/repos","events_url":"https://api.github.com/users/stapelberg/events{/privacy}","received_events_url":"https://api.github.com/users/stapelberg/received_events","type":"User","site_admin":false},"created_at":"2015-07-18T12:38:43Z","updated_at":"2015-07-18T12:38:43Z","body":"> That would also mean we don't really keep dead code around. Running RandR 1.5 and being able to do multiscreens should be enough (for now) to make sure our implementation works.\r\n\r\nThat way we could at least verify that things don’t break and that we support the monitor concept per se, yeah.\r\n\r\n> However, how do we want to deal with XCB? We can't really raise the dependency (is RandR 1.5 even supported in the latest XCB release or only in the development version (or not at all yet)?), which would leave us with having to deal with Xlib for RandR 1.5, correct?\r\n\r\nUgh, indeed. I confused randrproto and xcb-proto when looking at where it’s implemented so far. So, yes, we’d need to first update xcb-proto, then get libxcb rebuilt at least (a new release might not be necessary). We should definitely wait until an xcb version which supports this is available in the major distros."}}