You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hyprland, built from branch HEAD at commit 03ebbe18ed8517ee22591eac82cd54322f42cb7d (props: bump ver to 0.34.0).
Date: Mon Jan 1 12:03:15 2024
Tag: v0.34.0
Bug or Regression?
Bug
Description
When scrolling through the workspace using the workspace, e +/- 1 , the animation direction of going from workspace 1 to the the last is the same than going from 1 to 2. The same applies from going to the last to the first which is also reversed.
How to reproduce
Open at least 3 workspaces
Scroll between the first and the last
The animation is reversed which is confusing for navigation
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered:
This animation direction is intentional, as the last workspace is in the same direction as the second workspace from the perspective of the first workspace.
As far as I understood you want the option to have the following behavior instead:
The relevant code section determining the direction of this animation is in src/helpers/Monitor.cpp:527 in the changeWorkspace function which gets called in src/managers/KeybindManager.cpp:929. I won't implement a Pull Regest for this for now as it is quite late, but I might take another look at it tomorrow.
I propose animations:workspace_wraparound instead, it's more consistent with where other workspace animation setting are configured and imo is a more straightforward name
Hyprland Version
System/Version info
Bug or Regression?
Bug
Description
When scrolling through the workspace using the
workspace, e +/- 1
, the animation direction of going from workspace 1 to the the last is the same than going from 1 to 2. The same applies from going to the last to the first which is also reversed.How to reproduce
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: