sway-borders icon indicating copy to clipboard operation
sway-borders copied to clipboard

Allow per-window border configuration

Open OdiousImp2604 opened this issue 4 years ago • 2 comments

I'm pretty sure there's definitely a way to do this but using the for window [ app id ] etc; then using for example border pixel 1 or border none doesn't remove the image borders. I tried it without the image border ( on this fork just using normal border) and it worked fine.

sway version 1.5-64ea407f (Dec 18 2020, branch 'master')

for_window [app_id="avizo-service"] floating enable, border none This removes the border if i'm using normal borders but not when I'm using the images. I'm guessing there's perhaps another variable I should use but it's not documented....

#Borders
gaps inner 28
gaps outer -8
default_border none

border_images.focused ~/.config/sway/borders/focused.png
border_images.focused_inactive ~/.config/sway/borders/focused_inactive.png
border_images.unfocused ~/.config/sway/borders/unfocused.png
border_images.urgent ~/.config/sway/borders/urgent.png

Some relevant part of my config. 2021-01-12T16:52:43,035017360+00:00 If it helps.

OdiousImp2604 avatar Jan 13 '21 13:01 OdiousImp2604

I'm hesitant to call this a bug in sway-borders because this is knowingly left out. border_images apply generally to all containers/views and not individually to containers like the standard border pixel.

In this case, avizo shouldn't be asking to have borders drawn in the first place. I don't know much about Wayland, but I believe it should be using the layer-shell protocol, for which Sway won't draw borders for. Most notification daemons, bars, etc. use it.


Overall though, I think it would be great to support per-container border_images, so I'll leave this up as a feature request.

fluix-dev avatar Jan 13 '21 14:01 fluix-dev

Oh... sorry. Thank you for the information though!

OdiousImp2604 avatar Jan 13 '21 14:01 OdiousImp2604