aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-08-22scene_output_layout: make output adding explicitRose Hudson
Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3709
2023-08-22output_layout: return wlr_output_layout_output when adding outputRose Hudson
This will be used for the scene-graph integration.
2023-08-22wlr_output: Set current_mode during new custom modeAlexander Orzechowski
When setting a custom mode current_mode will not be reset. That means that next time the compositor tries to reset back from the custom mode, it will compare against the stale current_mode and unset WLR_OUTPUT_STATE_MODE erroneously.
2023-08-21compositor: drop wlr_surface_destroy_role_object()Simon Ser
This function is now unnecessary.
2023-08-21xdg-shell: rework rolesKirill Primak
2023-08-21xdg-popup: avoid using wlr_surface_destroy_role_object()Kirill Primak
2023-08-21Don't assume xdg_surface.{toplevel,popup} is non-NULLKirill Primak
This assumption will become incorrect with future commits.
2023-08-21xdg-shell: don't return anything from create_xdg_surface()Kirill Primak
2023-08-21egl: Don't assume display is owned when KHR_display_reference is unsupportedAlexander Orzechowski
We could potentially leak a display here, but not really because the display acts as a singleton that will be returned next time a renderer of the same device is created.
2023-08-21egl: Remove dead codeAlexander Orzechowski
Display is always NULL here since egl_init is always last to be called.
2023-08-21buffer: make wlr_client_buffer functions privateSimon Ser
We want to eventually remove this. Let's make sure compositors don't start using either of these functions.
2023-08-21backend/headless: fix broken output frame eventsSimon Ser
frame_delay was set to 0. Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3712
2023-08-20renderer/vulkan: Defer device lost signal until end of passAlexander Orzechowski
If the compositor were to try to handle a GPU reset within the lost signal (by recreating the renderer) we should avoid referencing renderer resources after the lost signal. This prevents use after free for such compositors.
2023-08-19xdg-decoration: store an xdg_toplevel instead of xdg_surfaceLeonardo Hernández Hernández
Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3685
2023-08-16backend/wayland: wait for xdg_surface.configure explicitlySimon Ser
We were assuming a roundtrip was enough to get an xdg_surface.configure event. That's not the case, the protocol spec doesn't make such a guarantee.
2023-08-16render: split render pass API into separate headerSimon Ser
Keeps the main wlr_renderer.h a tad more tidy.
2023-08-16wlr_output: Nuke wlr_output_update_enabledAlexander Orzechowski
2023-08-16output: Schedule mode updates to happen with rest of output eventsAlexander Orzechowski
2023-08-16output: Inline wlr_output_update_{custom,}_modeAlexander Orzechowski
2023-08-16wlr_output: Make wlr_output_update_{custom,}_mode privateAlexander Orzechowski
Backends should be using wlr_output_send_request_state to request modesets to the compositor. This will be inlined and removed next commit.
2023-08-16backend/drm: Use output state to set init modeAlexander Orzechowski
2023-08-16backend/drm: Move output variable up in connect_drm_connectorAlexander Orzechowski
2023-08-16backend/headless: Use output state to set init custom modeAlexander Orzechowski
2023-08-16backend/wayland: Use output state to set init custom modeAlexander Orzechowski
2023-08-16backend/x11: Use output state to set init custom modeAlexander Orzechowski
2023-08-16output: Add initialization state to wlr_output_initAlexander Orzechowski
2023-08-16output: Extract common commit logicAlexander Orzechowski
2023-08-16examples/embedded: new exampleSimon Ser
2023-08-16backend/wayland: add wlr_wl_output_create_from_surface()Simon Ser
By using this function, a compositor can display a wlroots compositor in a sub-surface, for instance.
2023-08-16backend/wayland: tag wl_surfaceSimon Ser
When integrating wlroots with another toolkit, wlroots may receive wl_pointer.enter events for surfaces not backed by a wlr_output. Ignore such surfaces by tagging the ones we're aware of with wl_proxy_set_tag().
2023-08-16backend/wayland: take existing wl_display in wlr_wl_backend_create()Simon Ser
This allows compositors to use an existing wl_display, to integrate wlroots with an existing toolkit.
2023-08-14renderer: Sanity check texture source boundsAlexander Orzechowski
2023-08-12screencopy_v1: Implement copy regions with gpu blit pathAlexander Orzechowski
2023-08-12screencopy_v1: Use new renderer API for gpu blit pathAlexander Orzechowski
2023-08-03Avoid using memcpy() to copy structsSimon Ser
We can just use a regular assignment instead. This is more type-safe since there is no need to provide the struct size. The remaining memcpy() calls perform array copies or copies from void pointers (which may be unaligned).
2023-08-03xwayland: drop wlr_xwayland_surface.events.set_pidSimon Ser
The PID of an X11 window cannot change. This is a remnant from the days when we queried the PID with a window property, instead of using XRes.
2023-08-03wlr_output: update cursor when scale changedJiDe Zhang
Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3699
2023-08-03wlr_output_cursor: assert renderer isn't NULLJiDe Zhang
When a wlr_output add to wlr_output_layout, wlr_cursor will create wlr_buffer of xcursor for the wlr_output, this behavior depends wlr_renderer of wlr_output, using assert to ensure renderer is initialized before wlr_output_layout_add and wlr_cursor_set_buffer/ wlr_cursor_set_xcursor.
2023-07-28xwayland: avoid calling xwm_get_atom_name() when debug logs are offSimon Ser
xwm_get_atom_name() performs a roundtrip to the X11 server. Avoid calling this blocking function if debug logs are turned off.
2023-07-27types/wlr_drm_lease_v1: downgrade DRM backend error message to debugSimon Zeni
Downgrades the error message printed out when no DRM backend is given from `WLR_ERROR` to `WLR_DEBUG`
2023-07-27render/vulkan: use renamed glslang binary by defaultq234rty
glslang 12.3.0 renamed glslangValidator to glslang, use that by default and use the old name as a fallback. References: https://github.com/KhronosGroup/glslang/blob/main/CHANGES.md?plain=1#L14
2023-07-26compositor: add "mapped" flag docKirill Primak
2023-07-26Unmap wlr_surface before making its role object inertKirill Primak
2023-07-26xwayland/shell: don't listen to wlr_surface.events.destroyKirill Primak
The wlr_xwayland_surface_v1 will be destroyed automatically from xwl_surface_role_destroy().
2023-07-26backend/drm: restore custom modesSimon Ser
We were only restoring fixed modes here. The DRM backend no longer creates fixed modes when the compositor sets a custom mode, so we need to handle this situation when restoring. Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3698
2023-07-26wlr_output: add comments for signal parametersrewine
2023-07-23xdg-shell: add support for v6Leonardo Hernández Hernández
This adds the suspended toplevel state
2023-07-24cursor-shape-v1: new protocol implementationSimon Ser
References: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/194
2023-07-22wlr_scene: Don't damage when setting opaque regionAlexander Orzechowski
Opaque region is a optimization hint, (bugs outstanding) it will not change the output contents, therefore damage does not need to be submitted. However, we still need to update the visibility state of the other nodes in the tree. To do this call scene_update_region() by ourselves but not `scene_node_update()` which will damage the outputs.
2023-07-22wlr_scene: Fix damage tracking with non atomic opaque region configurationAlexander Orzechowski
We need to intersect the opaque region with the node size or else we'll get damage tracking effects with compositors attempting to use wlr_scene_buffer_set_opaque_region() along with resizing the buffer at the same time in a certain order. Consider this: I have a new buffer that I want to commit to my scene buffer that is smaller than the old one. However, I still have the old opaque region that is the size of the old larger buffer, so that means that for the small moment between when we reconfigure the opaque region for the new buffer the opaque region will be oversized. Scene logic will then try to apply occluding optimizations outside of the node boundaries causing damage artifacts.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-26 08:31:07 +0000