Max Verevkin

> My goal was to allow i3bar to interpret the scroll wheel as a workspace change Well, this is already possible by adding appropriate click handlers for each block. Maybe...

> this is already possible by adding appropriate click handlers for each block I must mention that I'm talking about the master branch, not 0.22 release.

> Are clicking and scrolling considered the same thing though? Yes. This comes from the way i3 bar protocol works. > the default i3status must just not accept scrolling events...

> I will give that a try first to see if the behavior is the same It is the same... But it lets you assign custom handlers for scrolling "events".

Closing due to lack of activity

> It doesn't add any new dependencies Unfortunately it does: https://github.com/greshake/i3status-rust/pull/1471/commits/54223fb9f4cb63a7e943984879cfb537eb992e53

Would be nice if there was a `dlopen` version...

@dijit can you rebase please? The `Block` trait changed, see the definition [here](https://github.com/greshake/i3status-rust/blob/dc995ff35ff6364b9ce0f73ce73f815ea96e2ea0/src/blocks.rs#L64-L98). In short, `id()` was removed and `name()` was added. `block_error` function was removed, see what's available [here](https://github.com/greshake/i3status-rust/blob/master/src/errors.rs)....

Closing due to lack of activity

> I guess it is the result of /usr/lib/systemd/system/pacman-filesdb-refresh.timer I doubt it. I never used a timer or even `pacman -Fy` (this is what `pacman-filesdb-refresh` runs). It should be completely...