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
One of the recent versions (not sure which exactly) introduced a new bug, where the skipActive argument to ActivateAdjacent and MoveWindowToAdjacentWorkspace no longer seem to work. That is, calling
Butler.ActivateAdjacent(skipActive:true)
will activate the next workspace, even if it is active on another monitor, resulting in the two workspaces being swapped.
Behavior
One of the recent versions (not sure which exactly) introduced a new bug, where the
skipActive
argument toActivateAdjacent
andMoveWindowToAdjacentWorkspace
no longer seem to work. That is, callingwill activate the next workspace, even if it is active on another monitor, resulting in the two workspaces being swapped.
Similar, calling
will move a window to the next workspace, even if that is active on another monitor.
Config
https://github.com/urob/whim-config
The text was updated successfully, but these errors were encountered: