fork of wlroots with action binder support https://git.vlhl.dev/navi/wayland/wlroots.git/atom?h=master 2021-11-25T16:49:05+00:00 2021-11-25T16:49:05+00:00 Simon Zeni simon@bl4ckb0ne.ca 2021-09-30T14:53:18+00:00 urn:sha1:1d3dd7fc08f22f2e82cb812ced822369e984d845 2021-07-29T13:48:33+00:00 Simon Ser contact@emersion.fr 2021-07-12T15:52:44+00:00 urn:sha1:d17a0090627e4e477220dc5a846ff021e297ade5 We no longer require wlr_output_impl.{attach,rollback}_render to be populated. 2021-06-20T21:17:08+00:00 Simon Ser contact@emersion.fr 2021-06-18T10:15:08+00:00 urn:sha1:2f615468b68d49c8ec03ceffa751f8425d4c9b6b Right now, when a new output state field is added, all backends by default won't reject it. This means we need to add new checks to each and every backend when we introduce a new state field. Instead, introduce a bitmask of supported output state fields in each backend, and error out if the user has submitted an unknown field. Some fields don't need any backend involvment to work. These are listed in WLR_OUTPUT_STATE_BACKEND_OPTIONAL as a convenience. 2021-05-21T20:13:54+00:00 Simon Ser contact@emersion.fr 2021-04-28T22:07:31+00:00 urn:sha1:7ec5bf6b10d2a7e1d9cdfdfeed44ac6db8bdcc99 This new functions cleans up the common backend state. While this currently only emits the destroy signal, this will also clean up the renderer and allocator in upcoming patches. 2020-12-31T19:34:36+00:00 Ilia Bozhinov ammen99@gmail.com 2020-12-29T14:38:09+00:00 urn:sha1:eb30cde77751aaf11a6a754d053a50df5399739c 2020-06-19T19:07:24+00:00 Simon Ser contact@emersion.fr 2020-06-19T19:04:20+00:00 urn:sha1:c93016028680a0ce2bac2f2b8eeff5e5c1ea467e 3c5dbfd97c77 ("output: make rollback_render mandatory") makes a no-op output init fail without this function. 2019-12-30T18:21:11+00:00 Simon Ser contact@emersion.fr 2019-08-16T16:41:56+00:00 urn:sha1:5d1ba0f44687f49cd28fcd8f69abac3cb0e07eb8 This reverts commit 01f903874b7e27539488fad7f31476d5bcbc6ac9 and re-applies commit ee5f98ad49fed0439f3313ec685307831d1d1d05. Updates: https://github.com/swaywm/wlroots/issues/1640 (Atomic output updates issue) See also: https://github.com/swaywm/wlroots/pull/1762 (Atomic output updates original PR) See also: https://github.com/swaywm/wlroots/issues/1780 (Issue caused by atomic output updates) See also: https://github.com/swaywm/sway/issues/4419 (Issue caused by atomic output updates) See also: https://github.com/swaywm/wlroots/pull/1781 (Revert PR) 2019-12-23T12:48:29+00:00 Scott Anderson scott@anderso.nz 2019-11-22T07:11:15+00:00 urn:sha1:cff1c2f740a2f7d22339a0fae14c4923223a8d61 Bumps minimum version to 0.51.0 - Remove all intermediate static libraries. They serve no purpose and are just add a bunch of boilerplate for managing dependencies and options. It's now managed as a list of files which are compiled into libwlroots directly. - Use install_subdir instead of installing headers individually. I've changed my mind since I did that. Listing them out is annoying as hell, and it's easy to forget to do it. - Add not_found_message for all of our optional dependencies that have a meson option. It gives some hints about what option to pass and what the optional dependency is for. - Move all backend subdirectories into their own meson.build. This keeps some of the backend-specific build logic (especially rdp and session) more neatly separated off. - Don't overlink example clients with code they're not using. This was done by merging the protocol dictionaries and setting some variables containing the code and client header file. Example clients now explicitly mention what extension protocols they want to link to. - Split compositor example logic from client example logic. - Minor formatting changes 2019-08-07T07:22:11+00:00 Rouven Czerwinski rouven@czerwinskis.de 2019-08-07T06:11:38+00:00 urn:sha1:01f903874b7e27539488fad7f31476d5bcbc6ac9 This reverts commit ee5f98ad49fed0439f3313ec685307831d1d1d05. This intoduced problems where outputs could not be turned off because they had flips pending. 2019-08-02T14:01:29+00:00 Simon Ser contact@emersion.fr 2019-07-18T18:38:12+00:00 urn:sha1:ee5f98ad49fed0439f3313ec685307831d1d1d05 This commit makes more output properties (mode, enabled, scale and transform) atomic. This means that they are double-buffered and only applied on commit. Compositors now need to call wlr_output_commit after setting any of those properties. Internally, backends still apply properties sequentially. The behaviour should be exactly the same as before. Future commits will update some backends to take advantage of the atomic interface. Some backends are non-atomic by design, e.g. the X11 backend or the legacy DRM backend. Updates: https://github.com/swaywm/wlroots/issues/1640