after using xborders my cpu usage goes up to 30% even when no apps are running. is this normal ?\

EDIT: also when i go fullscreen in i3 i can still see the curved borders . How do i fix that?

Hi everybody, Using xborder I noticed that there is an annoying gap on all the "Jetbrains" products.

So I decided to investigate and I discovered the error: The problem is in the following line: https://github.com/deter0/xborder/blob/0a8e5c951806b0f30ddec59ce26677f7075cf9b2/xborders#L386

It seems that using window.get_geometry() can cause problems for some windows, so I replaced with window.get_client_window_geometry() and everything works fine for me.

In addition, I do some little refactoring in order to improve the code quality and readability.

Hope this can help.

I am currently using i3 and the border ignores the title bar. It would be cool if it also included the title bar.

for_window [class=".*"] title_format " %title" could be used to add a padding to the title bar text in i3 to not be obstructed by the rounded corners.

I don't know how easy this is to fix but a workaround would be allowing to set the radius of the corners individually. This allows settings the top left and top right corner to radius=0 which would at least result in rounded corners at the bottom.

Great work!

This is happening only with Webstorm (and I guess other IntelliJ-based programs; Might be related to Java programs in general?):

When opening webstorm, the top border created by xborder seems to be rendered at an offset of a good 15-20px higher than the window (See image):

I tried using --border-mode inside | outside | center but I still get the same result

WM: i3-gaps-rounded-git, version 4.20.1-98-ga70b89a7

I just saw your commit that fixed the mpv issue, so I installed the new version! You added a cool feature (I didn't really check the commits to see if it was intentional tho) that disables xborders when you fullscreen a window (on i3). I really liked it. But when you switch to another window and switch back to the maximized window, xborders reappears. Its a bit annoying in multiple monitor setups, but I can't see xborders using one display or when I have a maximized window on both screens.

Edit: I tested some gtk applications (gVIM, zathura, virt-manager) and I could see the xborders in the corner of them when their window was maximized.

There are some issues with the render position of the outline in i3, especially when using window borders and in tabbed layout.

These can be fixed while also improving performance by making use of the i3 IPC to listen to window events and retrieve the focused window dimensions.

I've implemented this in my fork along with some other QoL features (custom color, easy install through pip/pipx with feature switches, hide border in fullscreen). All very hacked together, so I'd be happy to re-implement those as separate PRs here if that's wanted.

This commit aim is to solve performance issues #17 and fix #18 The reason why the performance improvement is working is that calling subprocess.run or Popen in every drawing cycle is very expensive, because subprocess will call out to the shell which will execute xdotool or xprop after which we need to parse the output. Instead of these slow calls we should use Wnck.Window methods to get the same properties. This part of the refactoring caused a 5-10% performance improvement,

In the other hand I've removed the self.input_shape_combine_region(cairo.Region()) from _on_draw which caused another 15-20% improvement on CPU usage. I'm not sure why that line was there, so I've left it commented out with a TODO note for future removal.

Title, I wasn't able to find any options or docs on having the window applied to all window on the desktop. For some context I am using only I3 as a window manager without a desktop environment which maybe is causing this to happen if it not intended. Thanks!,

This PR aim is to resolve #16

• Add function to query a window map state using xwininfo command given an X window id
• There is a caching mechanism for querying window map state and storing it in viewable_window_map. Every half a second it will be updated for every window and to prevent this map to grow uncontrolled (when closing windows we don't want those items in our map) we need to cleanup somehow, the current logic is to throw the whole map and recreate it on demand.

"You could amend your readme to explain that one needs to set up rounded corners in picom.conf, set borders to 0 in the i3 config, that the picom corner radius should match `border-radius and give a short example json-file like

{
  "border-radius": 10, 
  "border-width": 5, 
  "border-rgba": "FFFF00FF" 
}

might seem obvious, but still...."

u/r_wraith on reddit

I've cleaned up some code and added a config.json file for customization. I also updated the README. No actual functionality has changed and it works as normal.

This adds some new options to the script, allowing you to have gradient borders.

The --border-gradient option accepts a list of RGBA colors, which will make up the gradient.

The --rainbow option will create a rainbow gradient (using the built in colorsys module's hsv_to_rgb) The --rainbow-steps option specifies how many colors the rainbow gradient should use, the default being 20. This can slightly affect performance, but around 20 seems to be the sweet spot where performance is good but both ends of the gradient are roughly the same color. The --rainbow-saturation option specifies the saturation of the colors in the rainbow gradient, this is nice to get a sort of pastel look. The --rainbow-brightness option specifies the brightness of the colors in the rainbow gradient, for customization and completeness.

The --absolute-gradient option makes the gradient 'absolute,' so it doesn't move with the current window. This gives the effect that the border is masking the gradient.

xborders: 3.2 (pulled today, 2022-10-05) OS: Debian Sid (unstable) 5.19.11-1 Host: 80S6 Lenovo N22 (amd64) Python: 3.10.7 WM: i3-gaps 4.21-18-gcee84a56

xborders isn't able to start:

❯ ./xborders
/home/a/git/xborder/./xborders:280: DeprecationWarning: Gtk.Window.set_wmclass is deprecated
  self.set_wmclass("xborders", "xborder")
Traceback (most recent call last):
  File "/home/a/git/xborder/./xborders", line 449, in <module>
    main()
  File "/home/a/git/xborder/./xborders", line 443, in main
    Highlight(screen_width, screen_height)
  File "/home/a/git/xborder/./xborders", line 298, in __init__
    self.input_shape_combine_region(cairo.Region())
KeyError: 'could not find foreign type Region'

I don't know if it is currently possible to do so, since there is no issue that states this problem, but some of my applications like xfdesktop, ulauncher and the GTK based applications look weird when used with xborders, on the GTK applications there is a big gap between xborders and the GTK application window, I guess probably because of GTK frames. I do want xborder to work with GTK applications, so if it is possible to fix it instead of adding GTK apps to blacklist, it would be amazing, something similar happens with ULauncher and xfdesktop is just a component of the xfce session so idk why it has borders.

The repository is named xborder, the window's role is xborder

The title of the README is xborders, the executable is xborders and xborders is used all over the README