From c4ff8701f149143e5e104e24dbca7a7b31e7a308 Mon Sep 17 00:00:00 2001 From: Michael Carlberg Date: Mon, 5 Dec 2016 14:01:34 +0100 Subject: [PATCH] Updated Module: bspwm (markdown) --- Module:-bspwm.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Module:-bspwm.md b/Module:-bspwm.md index 545d06c..e55fdc5 100644 --- a/Module:-bspwm.md +++ b/Module:-bspwm.md @@ -3,14 +3,18 @@ This module uses the bspwm ipc client to display information about available mon See the [Configuration wiki page](https://github.com/jaagr/polybar/wiki/Configuration#global-wm-settings) for details on how to configure the `_NET_WM_STRUT_PARTIAL` values. This will allow you to update `padding_{top,bottom}` when the bar is launched. -### Accesible desktop cycling +### Accesible workspace cycling You are able to define fallback click handlers for the whole bar window. Using those you could cycle your desktops by scrolling anywhere on the bar (except existing areas setup for the same button). You should probably disable scrolling for the module (`enable-scroll = false`) if you are using this method. +The messages `bspwm-desk{prev,next}` are handled internally by the running bspwm module and they will send the appropriate commands using the bspwm ipc. You can replace it by any other command if you want a different behavior + ~~~ dosini [bar/mybar] -scroll-up = bspc desktop -f prev.local -scroll-down = bspc desktop -f next.local +scroll-up = bspwm-desknext +scroll-down = bspwm-deskprev +;scroll-up = bspc desktop -f prev.local +;scroll-down = bspc desktop -f next.local ~~~