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
I don't want this to block 0.4.0, but I've realized the proper way to handle differently-sized monitors for monitor-* commands without waiting for the big rework needed to track what edge a window was originally tiled relative to.
Instead of clipping the target rectangle, or dumbly shoving the entire thing to be within the monitor's bounds, move it just enough to ensure that some minimum width (100px?) of the titlebar will be visible.
That way, if the window extends far enough into common subset of the monitor areas, it'll remain unmoved and behave like GTK+ 2.x QuickTile for cycling through monitors, but it won't be possible to lose a window off the edge of the desktop like Kubuntu 16.04 LTS allows in the absence of any kind of clamping.
The text was updated successfully, but these errors were encountered:
I don't want this to block 0.4.0, but I've realized the proper way to handle differently-sized monitors for
monitor-*
commands without waiting for the big rework needed to track what edge a window was originally tiled relative to.Instead of clipping the target rectangle, or dumbly shoving the entire thing to be within the monitor's bounds, move it just enough to ensure that some minimum width (100px?) of the titlebar will be visible.
That way, if the window extends far enough into common subset of the monitor areas, it'll remain unmoved and behave like GTK+ 2.x QuickTile for cycling through monitors, but it won't be possible to lose a window off the edge of the desktop like Kubuntu 16.04 LTS allows in the absence of any kind of clamping.
The text was updated successfully, but these errors were encountered: