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
Dual Monitor - different scaling - Dash between monitors - dash scaling is broken when having auto hide on, with animation duration - Proposed workaround
#2339
Open
frederikb96 opened this issue
Nov 28, 2024
· 0 comments
Laptop on the most left has scaling set to 175%, others 100%
Now the problem is that when we have default auto hide dash settings:
And the dash is positioned on left edge of second monitor. When moving the mouse to unhide the dash when an app is in fullscreen, we get this weird scaling behavior as shown in video:
out.mp4
But as in the video shown, this can easily be fixed with setting the animation time to 0. (I also set the timeout and pressure threshold, but that was just nicer for me, not necessary to fix the problem.
So with this it works.
Opened this issue, since default settings are having animation on, and others might have same problem, would be nice if this scaling problem is fixed at some point :) But for now, this solution is totally fine, so hopefully helpful for others
The text was updated successfully, but these errors were encountered:
I have monitors next to each other:
Laptop on the most left has scaling set to 175%, others 100%
Now the problem is that when we have default auto hide dash settings:
And the dash is positioned on left edge of second monitor. When moving the mouse to unhide the dash when an app is in fullscreen, we get this weird scaling behavior as shown in video:
out.mp4
But as in the video shown, this can easily be fixed with setting the animation time to 0. (I also set the timeout and pressure threshold, but that was just nicer for me, not necessary to fix the problem.
So with this it works.
Opened this issue, since default settings are having animation on, and others might have same problem, would be nice if this scaling problem is fixed at some point :) But for now, this solution is totally fine, so hopefully helpful for others
The text was updated successfully, but these errors were encountered: