-
Notifications
You must be signed in to change notification settings - Fork 342
Make wlr_output_enable idempotent #3306
base: master
Are you sure you want to change the base?
Conversation
|
The only time this change will have any effect is if |
I don't understand which kind of issues you're running into. If |
I will do some testing locally. |
Without this commit my compositor trips over this assertion. |
This is a glue file to allow integration with builds.sr.ht.
wlroots has migrated to gitlab.freedesktop.org. This pull request has been moved to: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/3306 |
For `required` to disable search the value needs to be of `feature` type. Checking `gles2` via `in` keyword returns a `bool` but `required: false` makes the dependency optional instead of disabled.
This allows compositors to handle touch pointer emulation manually, instead of having Xwayland do it [1]. [1]: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/691
This struct contains additional information for session device change events, such as the DRM connector ID that has changed.
When a connector ID is specified in a hotplug event, don't scan all connectors. Only scan the connector that has changed.
Callers can access output->front_buffer instead.
The protocol uses a signed integer here, which is also what the wlr_input_method_v2_preedit_string struct provides to compositors from the input method protocol. Sway currently just passes those int32_t values directly to this function leading to an implicit conversion.
Closes #3324.
Removing an input device requires unlinking it from the list of all headless input devices. For that implement a destroy function.
We were send a protocol error if INTERLACED or BOTTOM_FIRST was set. This is incorrect for the zwp_linux_dmabuf_params.create code-path because this kills the client without allowing it to gracefully handle the error. We should only send a protocol error if the client provides a bit not listed in the protocol definition.
They are never used in practice, which makes all of our flag handling effectively dead code. Also, APIs such as KMS don't provide a good way to deal with the flags. Let's just fail the DMA-BUF import when clients provide flags.
A wlroots user can easily get confused and think that `cap` refers to wlroots buffer capabilities, not array capacity.
Co-authored-by: Simon Zeni <[email protected]>
Enabling or disabling an output should be idempotent. Previously, this was not the case, causing bugs.
ab53f5e
to
7375cfa
Compare
Enabling or disabling an output should be idempotent. Previously, this
was not the case, causing bugs.