aboutsummaryrefslogtreecommitdiff
path: root/src/LayerMenu.hh
diff options
context:
space:
mode:
authorMark Tiefenbruck <mark@fluxbox.org>2021-07-06 23:56:20 (GMT)
committerMark Tiefenbruck <mark@fluxbox.org>2021-07-06 23:56:20 (GMT)
commit8bc11006a5ac8c10a539e5a38cdf62205ff386ad (patch)
tree54e3ef1fe6fb25f56d59d9b9e96b4eec6467ef82 /src/LayerMenu.hh
parent0279936d835d7d88537bcf1208035787c02ced59 (diff)
downloadfluxbox-8bc11006a5ac8c10a539e5a38cdf62205ff386ad.zip
fluxbox-8bc11006a5ac8c10a539e5a38cdf62205ff386ad.tar.bz2
Patch from Glen Whitney
A priori, there is no reason why the workspace warping functionality should treat the horizontal and vertical directions at all differently. Even if traditionally horizontal warping was more common, for some in recent times as aspect ratios tend to become larger, stacking virtual workspaces vertically may make more sense. Similarly, some might want to traverse an array of workspaces in column-major, rather than row-major, order. Prior to this commit, there were extra parameters for vertical warping (a controlling flag and an offset for how many workspaces to jump) as opposed to horizontal warping. Also it was impossible to allow vertical warping while disallowing vertical warping. This commit makes all of the parameters and behavior for horizontal and vertical warping equivalent. For backwards compatibility, there is an overarching flag controlling whether warping occurs at all, as well as a separate control flag and offset for each of horizontal and vertical warping. The relevant init file resources and default values are: session.screen0.workspaceWarping: true session.screen0.workspaceWarpingHorizontal: true session.screen0.workspaceWarpingVertical: true session.screen0.workspaceWarpingHorizontalOffset: 1 session.screen0.workspaceWarpingVerticalOffset: 1
Diffstat (limited to 'src/LayerMenu.hh')
0 files changed, 0 insertions, 0 deletions