awesome wm - Start client fullscreen doesn't cover wibox -
when client started, should started fullscreen. tried configure using rules no matter do, client doesn't cover wibox.
what have far:
function set_fullscreen(c) mywibox[c.screen].ontop = false c.fullscreen = false c.fullscreen = true c.x = 0 c.y = 0 mywibox[c.screen].ontop = false c.fullscreen = false c.fullscreen = true c.x = 0 c.y = 0 end awful.rules.rules = { { rule = { }, properties = { border_width = beautiful.border_width, border_color = beautiful.border_normal, focus = awful.client.focus.filter, keys = clientkeys, buttons = clientbuttons } }, { rule = { class = "<name>" }, properties = { fullscreen = true, size_hints_honor = false, focus = true }, callback = set_fullscreen } }
i have wibox on bottom , application gets painted above wibox. gets painted off-screen above, size of wibox. application seems have correct size, wibox seems in way.
when toggle fullscreen application, when running, fullscreen works expected. application cover wibox.
function toggle_fullscreen(c) c.fullscreen = not c.fullscreen end
i have signal handler toggles ontop wibox when focussed client's fullscreen property changes:
client.connect_signal("property::fullscreen", function (c) if c.fullscreen , c == client.focus mywibox[c.screen].ontop = false else mywibox[c.screen].ontop = true end end)
nothing seems start application in fullscreen, have toggle manually. idea doing wrong?
client.connect_signal("property::fullscreen", function (c) if c.fullscreen , c == client.focus mywibox[mouse.screen].visible = not mywibox[mouse.screen].visible else mywibox[mouse.screen].visible = not mywibox[mouse.screen].visible end end)
work me.
Comments
Post a Comment