Enable XWayland only for skinned UI (part 1)#1747
Open
jlindgren90 wants to merge 1 commit intoaudacious-media-player:masterfrom
Open
Enable XWayland only for skinned UI (part 1)#1747jlindgren90 wants to merge 1 commit intoaudacious-media-player:masterfrom
jlindgren90 wants to merge 1 commit intoaudacious-media-player:masterfrom
Conversation
Needs accompanying change on plugins side
Member
|
As suggested in https://github.com/orgs/audacious-media-player/discussions/1664 it would be nice to have a configuration option for Xwayland. My idea for this would be:
What do you think? |
Member
Author
|
I'm fine with adding configuration option but I think we still need to force XWayland for the skinned UI, it's basically unusable otherwise. |
This file contains hidden or 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
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.
The newer (GTK and Qt) UIs are mostly usable with native Wayland. Undocked plugins are still problematic, since positions are not saved/restored, but (1) keeping them docked is a workaround and (2) maybe it's time to let the problem be more visible so it gets solved?
Needs accompanying change on plugins side.