Age | Commit message (Collapse) | Author |
|
By adding a sent_feedback bool into the list entry that we can mutate
we no longer need to maintain this `sent_direct_scanout_feedback` variable.
sent_feedback will also be useful for output layers.
|
|
We will be able to add more state here
|
|
|
|
When an output is added to wlr_cursor, update its cursor image.
Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2119
|
|
Sets the cursor image for each output depending on the wlr_cursor
state.
|
|
Will be useful to apply the current cursor to new outputs.
|
|
Most of the surface-related state does not need to be per-output.
Move it to wlr_cursor_state.
|
|
|
|
Removes one allocation, makes this a bit more consistent with the
rest of wlroots.
|
|
This fixes an issue where the panel_orientation parameter was set but wlroots was ignoring it and
returning OUTPUT_TRANSFORM_NORMAL.
Fixes 2e12de96
|
|
|
|
|
|
Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3593
|
|
|
|
|
|
The sway scene port relies on this to create a copy of the buffer for
saved surface purposes.
|
|
|
|
|
|
Leave it up to the compositor to enable new outputs (just like the
DRM backend does).
|
|
|
|
|
|
We have nothing to do when a headless output is enabled/disabled.
|
|
A no-op commit should not schedule a new frame. This aligns the
headless backend with the rest of the backends.
This will be important to handle the enabled → disabled transition.
|
|
|
|
|
|
Removes duplication across all the backends to finally apply the mode
to the output.
|
|
|
|
|
|
Nobody remembers why this is done and it isn't that great if people
use a lot of custom modes.
|
|
If we are only rendering within a region of the surface that is
advertised as opaque, we can choose no blending
|
|
We're using both APIs at the same time.
|
|
wlr_output_update_needs_frame() is called unconditionally at the
end of the function already.
|
|
|
|
This changes the semantics of wlr_output_state. Instead of having
fields with uninitialized memory when missing from the committed
bitflag, all fields are always initialized (and maybe NULL/empty),
just like we do in wlr_surface_state. This reduces the chances of
footguns when reading a field, and removes the need to check for
the committed bitfield everywhere.
A new wlr_output_state_init() function takes care of initializing
the Pixman region.
|
|
Call wlr_surface_destroy_role_object() when the role_resource is
destroyed.
|
|
This increases type safety, makes it more obvious that role_data
must represent the role object, and will allow for automatic
cleanup when the resource is destroyed.
|
|
This checks the resource type before casting its user data pointer.
|
|
|
|
|
|
|
|
Destroying the liftoff_device invalidates all of the liftoff_planes.
Destroy the liftoff_planes before the liftoff_device to fix this.
|
|
This fixes a use-after-free in the Sway patch to filter the Xwayland
shell [1].
The server is destroyed first, then the shell. The Xwayland process
might still be using the shell while running.
When the shell is destroyed, libwayland will invoke the global
filter (to figure out whether to send a wl_registry.global_remove
to clients). Then Sway will compare the client with
wlr_xwayland_server.client. However, at that point, the server is
gone.
Reset the server to NULL so that Sway can check whether the server
is still running.
[1]: https://github.com/swaywm/sway/pull/7647
|
|
|
|
This function returns a bool, not a pointer.
|
|
|
|
|
|
...texture view is dynamically created
|
|
|
|
We need to always unlink the resource, even if it's already inert.
seat_client_destroy_*() may be called multiple times on the same
resource.
Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3638
|
|
This allows us to use the new render pass API, and drops some
implicit state usage.
|