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
It doesn't happen all the time. For me personally, not really a big issue, but just posting to see if anyone else is experiencing the same.
2024-11-16.18-56-54.mp4
The setup from the video:
0px outer_gap in glazewm.
has dock enabled to bottom, 0px margin on all 3 monitors.
Windhawk enabled for the Taskbar.
I was also able to reproduce this bug by reverting all changes I made prior to upgrading to v3.6.0:
40px outer_gap (top) in glazewm.
zebar on the top_left, no dock.
taskbar autohide, no windhawk.
You'll see me pressing alt+f in the video, that's to toggle out of fullscreen.
Now, before any of the devs go look into it, I will say that this might be a "rare" case, and just not worth fixing.
My 3rd monitor (to the right, not in video, is plugged through a USB-to-VGA adapter which works ok, but a bit laggy. So you know, it may be because of that.
Current docking feature is worth over this little "bug", so I'm not going back to 3.5.0.
Reproduction
Open any window and move it from one monitor to another, sometimes it can happen on the first try.
I've tried several combinations to nail down how and when it happens, but couldn't really, some cases were just rarer than others.
Empty monitor, incoming tiled window. (like in the video)
Non-Empty monitor, incoming tiled window. (didn't happen in video, but happened outside of recording)
Apps, I thought it only happened to more "heavy" apps like the browser or vscode. but sometimes it happens to the terminal as well, just less often.
Stack trace or error logs (if applicable)
No response
Version number
3.6.0
The text was updated successfully, but these errors were encountered:
Describe the bug
It doesn't happen all the time. For me personally, not really a big issue, but just posting to see if anyone else is experiencing the same.
2024-11-16.18-56-54.mp4
The setup from the video:
I was also able to reproduce this bug by reverting all changes I made prior to upgrading to v3.6.0:
You'll see me pressing
alt+f
in the video, that's to toggle out of fullscreen.Now, before any of the devs go look into it, I will say that this might be a "rare" case, and just not worth fixing.
My 3rd monitor (to the right, not in video, is plugged through a USB-to-VGA adapter which works ok, but a bit laggy. So you know, it may be because of that.
Current docking feature is worth over this little "bug", so I'm not going back to 3.5.0.
Reproduction
Open any window and move it from one monitor to another, sometimes it can happen on the first try.
I've tried several combinations to nail down how and when it happens, but couldn't really, some cases were just rarer than others.
Stack trace or error logs (if applicable)
No response
Version number
3.6.0
The text was updated successfully, but these errors were encountered: