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
While changing the position of overlay the "overlay move orders" can be queued (supposedly infinitely), this can lead to the situation shown in the attached gif. This makes entire WM unresponsive(you can see me trying to change workspace and press some keybindings), and any commands entered while animations are playing are added to queue and get executed all at once after animations are done. If "move orders" are spammed a lot, even the time displayed in the topbar will slowly get late. While spamming "overlay move orders" i probably not an usual use case for what overlay is, i think that it should only accept next "overlay move order" after current has finished, so we can avoid situations where you spam "move orders" and then have to wait 5 minutes in order to do anything.
The text was updated successfully, but these errors were encountered:
Also if I have a great lot of tabs open in a window (e.g. firefox), and I close said window, the window lingers for a very long while at the bottom edge of the screen before finally ending the animation and closing.
While changing the position of overlay the "overlay move orders" can be queued (supposedly infinitely), this can lead to the situation shown in the attached gif. This makes entire WM unresponsive(you can see me trying to change workspace and press some keybindings), and any commands entered while animations are playing are added to queue and get executed all at once after animations are done. If "move orders" are spammed a lot, even the time displayed in the topbar will slowly get late. While spamming "overlay move orders" i probably not an usual use case for what overlay is, i think that it should only accept next "overlay move order" after current has finished, so we can avoid situations where you spam "move orders" and then have to wait 5 minutes in order to do anything.
The text was updated successfully, but these errors were encountered: