fix, default to true, sway/workspaces: warp-on-scroll #2293
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
|
Can we have a new release with this fix? The regression cause by this bug is massive and makes GUI applications near unusable for me. |
|
@Alexays please note whynothugo's comment |
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.
Sorry about that, @q234rty correctly pointed out that my previous already merged pull request for a new feature did not default to the old behavior.
While I don't understand why anyone wouldn't use this feature if they already are using mouse_warp, since I can't read out the current status of the mouse_warp option, having this default to being enable disturbs people who don't use mouse_warp also, which I totally see is a preferential subject. So until there is a way to read the current status of mouse_warp, this has to default to the old behavior.