aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-10-30backend: drop wlr_backend_get_presentation_clock()Simon Ser
We can just assume CLOCK_MONOTONIC everywhere. Simplifies the backend API, and fixes clock mismatches when multiple backends are used together with different clocks.
2023-10-29xdg-toplevel: don't send maximized if tiled is requested but not supportedKirill Primak
This is a bit too magical and may break compositors which try not to send duplicate configure events.
2023-10-26xwayland: add wlr_xwayland_set_workareas()John Lindgren
This function allows compositors to set the _NET_WORKAREA property on the root window. XWayland clients use _NET_WORKAREA to determine how much of the screen is not covered by panels/docks. The property is used for example by Qt to determine areas of the screen that popup menus should not overlap (see QScreen::availableVirtualGeometry).
2023-10-26util/token: add docsSimon Ser
2023-10-26util/token: rename TOKEN_STRLEN to TOKEN_SIZESimon Ser
TOKEN_STRLEN is not actually the strlen() of the token. It's the size taken by the token included the final zero byte. Change the name to make this clearer, and remove unnecessary +1's.
2023-10-26render/vulkan: use VK_KHR_global_priorityeri
References: #3386
2023-10-26xdg-shell: use wlr_surface.unmap_commitKirill Primak
2023-10-26render/vulkan: remove unused queue_props in rendererSimon Zeni
2023-10-26layer-shell: track surface init stateKirill Primak
2023-10-26layer-shell: don't use wlr_surface_role.unmap hookKirill Primak
A layer-shell surface can be unmapped if wlr_layer_shell_v1 is destroyed or the client has committed a NULL buffer. Let's use the previously introduced wlr_surface.unmap_commit to handle the latter case instead; this is more consistent with the xdg_surface implementation logic, where using the hook is more trouble than it's worth. Additionally, this commit adds an unconditional surface reset on destroy, so popups are properly cleaned up even if originally created with an unmapped layer-shell surface as a parent. Doing so with the role unmap hook would either result in possibly resetting the surface twice, which is suboptimal, or having an awkward `if (mapped) { unmap() } else { reset() }` check.
2023-10-26compositor: add wlr_surface.unmap_commitKirill Primak
This flag can be used to figure out whether a particular commit has unmapped the surface. Private state for now in case we find a better way to track this.
2023-10-26layer-shell: check the configured flag earlierKirill Primak
2023-10-25examples: drop dead client codeSimon Ser
Client examples have been moved to another repo, but it seems I forgot to delete some files. Fixes: 0bb445eeffc5 ("examples: split clients in separate repository")
2023-10-21renderer/vulkan: don't add two alphas together in blend funcBrett Ernst
2023-10-19linux_dmabuf_v1: convert to try_fromeri
References: wlroots/wlroots#884
2023-10-19drm: convert to try_fromeri
References: wlroots/wlroots#884
2023-10-19buffer: convert to try_fromeri
References: wlroots/wlroots#884
2023-10-17render/vulkan: undo alpha premult before sRGB encoding/decodingSimon Ser
sRGB encoding/decoding needs to happen with straight alpha, not pre-multiplied alpha.
2023-10-16Fix output layers order error on wayland backendJiDe Zhang
2023-10-14xwayland: stop translating _NET_WM_STRUT_PARTIAL coordinatesJohn Lindgren
Translating the right/bottom coordinates from offsets to absolute coordinates in wlroots (rather than in the compositor) was supposed to be more reliable, since wlroots had access to the X11 screen size. It ended up being less reliable, because the screen size values (xwm->screen->width_in_pixels/height_in_pixels) are not updated when the output layout changes. So let's remove the translation from wlroots, and let the compositor figure it out. From what I can understand of the current XWayland code, the X11 screen size should generally match the overall wlr_output_layout bounding box, which the compositor has access to.
2023-10-12examples: split clients in separate repositorySimon Ser
The client examples are useful to try out protocols, however they don't need to live in the wlroots repository. Having both clients and compositors in the same place is confusing. The wlroots API changes often but protocols are set in stone.
2023-10-12Revert "backend/drm: Automatic non-blocking commits"Simon Ser
This reverts commit 45ba35719e874f7e8651e088c0582fe50301e731. Sadly, this causes regressions on amdgpu [1] and even with these fixed, there are fundamental issues with non-blocking modesets [2]. [1]: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3745 [2]: https://oftc.irclog.whitequark.org/dri-devel/2023-10-11#1697031838-1697036920;
2023-10-12build: rename libdrm partial dep to be more explicitSimon Ser
The variable is named "libdrm" but it's a partial dependency with just the headers. Reflect this in the name to avoid confusion (Meson variables are global to the whole project).
2023-10-10Drop wl_client and user data assertions in bind handlersKirill Primak
A client can never be NULL and user data assertions aren't really useful there.
2023-10-10xwayland: add wlr_xwayland_create_with_server()Simon Ser
Allows compositors to set up the server (and shell) on their own.
2023-10-10xwayland/server: add ready flagSimon Ser
Allows one to check whether the server is currently ready.
2023-10-10backend/drm: Automatic non-blocking commitsKenny Levinsen
We currently only perform non-blocking commits for non-modeset commits with a buffer attached. Perform non-blocking commits whenever there is no pending pageflip event. If a non-blocking modeset commit fails, which can happen if the driver implicitly added more CRTCs to the commit that we did not know we had to wait for, retry with a blocking commit. References: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2239
2023-10-10docs: add architecture documentSimon Ser
2023-10-10security-context-v1: add commit eventSimon Ser
2023-10-10security-context-v1: new protocol implementationSimon Ser
Co-authored-by: Puck Meerburg <puck@puckipedia.com> References: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/68
2023-10-09xwayland: fix memory leakChristopher Snowhill
Fixes: f5797be8a8d410e22fa6397b2217a6a81858d05c Thanks to tesselslate on IRC for reporting. Signed-off-by: Christopher Snowhill <kode54@gmail.com>
2023-10-09xdg-shell: fix wlr_xdg_popup_destroy() docsKirill Primak
2023-10-09layer-shell: check for NULL in wlr_layer_surface_v1_destroy()Kirill Primak
2023-10-09output: allow_artifacts -> allow_reconfigurationKenny Levinsen
The name "allow_artifacts" and associated description is very vague, and theoretically allow for tearing behavior. Clarify that we only intend to mean artifacts related to output configuration (e.g., modesets). References: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3740
2023-10-08scene/output_layout: Add assert for duplicate output insertionAlexander Orzechowski
Ensure that the output was not added multiple times to the scene output layout.
2023-10-08Add GitLab issue templateSimon Ser
Add recommendations for the most common mistakes when reporting an issue.
2023-10-08util/addon: make wlr_addon_set_finish() saferKirill Primak
wl_list_for_each_safe() breaks if an item immediately after the current one is removed, see https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4358#note_2106260.
2023-10-08scene-output-layout: assert lo->output == so->outputKirill Primak
2023-10-07scene_output_layout: Don't destroy output when output layout is destroyedAlexander Orzechowski
There were a couple of problems with this: 1. The behavior is unexpected. Typically objects in wlroots won't also destroy objects that they depend on. For instance, wlr_scene_output will not destroy the wlr_output when it's destroyed. It shouldn't be any different for scene layouts. 2. This fixes a crash where because wlr_output_layout and wlr_scene_output are both addons to wlr_output, we might get into a situation where wl_list_for_each_safe might malfunction. See [1] This means that the compositor needs to manually destroy the output when they destroy the layout, hence ~breaking. Compositors can just call `wlr_scene_output_destroy()` if they want to destroy both at the same time. [1] https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4358#note_2106260 This reverts commit 1a731596c5bcd252d8796cacb59af8b20ceb914f. Co-authored-by: Kirill Primak <vyivel@eclair.cafe>
2023-10-06output_event_commit: Remove committed and bufferAlexander Orzechowski
The newly introduced state struct can be used to retrieve this.
2023-10-06wlr_output: Add applied state to commit eventAlexander Orzechowski
2023-10-06render/allocator: log message when GBM is disabledSimon Ser
When the backend and renderer would need GBM but it's disabled at compile-time, log a message to make this situation easier to debug.
2023-10-06render: log error when requested renderer is compile-time disabledSimon Ser
It can be a bit confusing to debug when the user requests an explicit renderer but it's disabled at build-time. Log an error when that happens.
2023-10-06seat: remove wlr_seat_validate_grab_serial()Kirill Primak
It makes little sense to have a catch-all grab vaildation function, considering that e.g. tablet tool implicit grabs are possible as well. Besides, the function has always returned true anyway.
2023-10-06xwayland: batch client ID request with other property requestsSimon Ser
2023-10-06xwayland: batch property requests when handling new windowSimon Ser
Instead of sending one request, waiting for the reply, and repeating for all properties we're interested in, we can send all property requests in one go and then wait for the server to reply.
2023-10-06xwayland: fix double free wlr_xwayland_shell_v1JiDe Zhang
2023-10-05render/drm_format_set: use published kernel doc URLSimon Ser
The kernel patch has been merged, so this is available in the official docs now.
2023-10-05render/vulkan: constrain blend to output subpass to redrawn regionManuel Stoeckl
This commit only applies to the render pass API.
2023-10-05util: add struct to track union of rectanglesManuel Stoeckl
The new struct rect_union is designed to make it easier to efficiently accumulate a list of rectangles, and then operate on an exact cover of their union. Using rect_union, the times needed to added t rectangles, and then compute their exact cover will be O(t), and something between Ω(t) and O(t^2), depending on the rectangle arrangement. If one tries to do the same by storing a pixman_region32_t and updating it with pixman_region32_union_rect(), then total time needed would be between Ω(t^2) and O(t^3), depending on the input. Without changing the public API (data structure + rectangle ordering rules) for pixman_region32_t, it is impossible to improve its worst case time.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-26 15:48:23 +0000