David Kosorin

All these dynamically generated properties are theme related properties (`or beautiful["checkbox_"..prop]`). `checked` should have custom getter/setter and could also handle the indeterminate (`nil`) state that is often available on checbox...

You should place the `constraint` widget into the `place` widget and set `halign`: ```lua { widget = wibox.container.place, halign = "center", { wibox.widget.progressbar, height = 5, width = 200, widget...

Just regular `mouse::*`/`button::*` signals. Here is `rc.lua` where you can try it: 1. press and hold mouse button on "foo" 2. move cursor over "bar" (the same wibox) => output...

`type` property doesn't have any effect in awesome wm. It only sets `_NET_WM_WINDOW_TYPE` on window. You can use [`wibox:struts()`](https://awesomewm.org/apidoc/popups_and_bars/wibox.html#struts) function to manually modify workarea. Or just use `awful.wibar` > awful.wibar...

Sorry. Somehow I missed this. It's actually a useful feature. I need to find another keybinding, because there is a conflicting "Move" keybinding (super+shift+arrows).

There is no prebuilt widget. Personally, I don't use this kind of widgets, so I didn't make them (yet).

https://discord.gg/xNkBzE6f

You can join the (non official) awesome wm discord community: https://discord.gg/BPat4F87dg

Can you verify that you can open Unity with the default awesome config?

> regarding keygrabber question, i'll need first to understand: > > 1. what was the initial intention of returning it there > > 2. why it's not possible to do...