Use layer-shell-qt for Desktop under Wayland
#1876
Merged
+30
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, workarounds provided by some Wayland compositors (like LabWC) were needed for having a usable Desktop under Wayland. With this simple patch, and thanks to the developers of `layer-shell-qt`, PCManFM-Qt's Desktop is completely ready for Wayland. Don't forget to remove probable workarounds before using it. Closes #1871
|
GTM "Let's give it to git users" (cit.) |
|
Maybe the AUR packages should be updated for all the merged Qt6 branches? Oh, I see |
Agreed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, workarounds provided by some Wayland compositors (like LabWC) were needed for having a usable Desktop under Wayland.
With this simple patch, and thanks to the developers of
layer-shell-qt, PCManFM-Qt's Desktop is completely ready for Wayland. Don't forget to remove probable workarounds before using it.Closes #1871