search

nwg-piotr / autotiling

Script for sway and i3 to automatically switch the horizontal / vertical window split orientation
GNU General Public License v3.0
930 stars 30 forks source link

Moving containers become stuck #19

Closed travankor closed 3 years ago

travankor commented 4 years ago

Testing autotile on the latest sway+wlroots git, I noticed that moving containers with the keyboard sometimes will be broken (moving containers with mouse still works). The only way to be able to move containers again is to kill the autotile script when this happens. Not sure how this happens exactly, but wanted to ask if anyone knows.

Running the manual version in case that's relevant.

nwg-piotr commented 4 years ago

Anyone else experienced such a behavior? More info needed.

travankor commented 4 years ago

Looking at the recent sway PR's, it seems like there are some regressions with i3 compatibility, so this might be the reason.

nwg-piotr commented 4 years ago

You mean: it only happens on the development version of sway?

travankor commented 4 years ago

No, I mean that there are some regressions in 1.5+ (1.5 was tagged in mid-July). But this is only noticed and getting fixed right now.

nwg-piotr commented 4 years ago

Ah, OK.

jboyens commented 3 years ago

I'm seeing the same thing on swaywm master as of the time of this message.

I've had to disable this to restore the functionality for the time being.

I did turn on debugging and the console just spits out Debug: Switched to splitv with each attempt to move a window. Windows that are in a stack seem to be able to move (once) and windows that are on separate outputs seem to be able to move from left to right across the monitor border (but not back left).

jboyens commented 3 years ago

I was unclear above.

When I said "windows that are in a stack", I meant windows that are in a splith together. The bottom window can move, but the top window cannot. I forgot about the explicit "stacking" support and that could be confusing for anyone else reading this.

travankor commented 3 years ago

Fixed with 1.6.